Is it true that when running a saved search from a Scheduled Script on a OneWorld account, the date filters and results are interpreted in the parent subsidiary's time zone? Context: I work for an organization in CT (Chicago) time zone, but their parent subsidiary is configured in CET (Europe/Amsterdam) time zone, and I'm getting unexpected search results. I'm using a relative

on or after x days ago

filter. How do I fix this? Load the search, calculate the date-time for the filters and then add them through script?

its more nuanced than that, if your script is running as the system user, then it uses the parent subsidiary's timezone

@battk Thanks for the input. I'm filtering on

datecreated

- won't the date depend on the time zone then? I think I'd have the same issue with the

hours ago

filter.

it does, date created is a datetime