Hi, we’ve identified a possible time zone issue with the webscrape function. For several of our customers, the scraped opening times consistently differ from the actual times shown on the websites. Example: For “Museum der Bildenden Künste” the website shows "geöffnet bis 18 Uhr" (left side of the screenshot), but the scraped result shows "geöffnet bis 12 Uhr" (right side of the screenshot) – a 6‑hour offset. This happens across multiple pages. We are located in MEZ / UTC+1, so we’re wondering if the scraping is happening in a different time zone and therefore saving incorrect values. Could you please check whether this is a time zone bug in the scraping pipeline? Thanks! https://cdn.discordapp.com/attachments/1451517768360001709/1451517769060192466/Screenshot_2025-12-18_124933.png?ex=6979e144&is=69788fc4&hm=45e36762b248b3e858a1446693ae42ceb3d30df619036c39e4d5a921ae251958&

Hello @t.zeidler , yes this could from the website giving different time based on the timezone .

Hi, are you able to give me an update on that? What is the solution?

The website is showing dynamic timing and the scraper has a different timing than the one you want, if the time is the only issue , you can include the times you want in the prompt instead of the KB.

Yeah, it's only a time issue, but that's appearing on several pages that were scraped. Is there a general prompt addition, that can be used (like "transform all times from [time zone] to CET"?) or do I need to fix the prompt for every single source where that problem shows up?

Yes, you can do that, prompt it to convert the business hour from [time zone] to CET, you can do that on the main global prompt.