Hi @Or Avidov & @tanu, I know this is an old thread but seems to be the same issue we're facing and wanted to check if there was already a solution. Trying to run a

volume_anomalies

test at a scheduled time each day for the prior day (for context, we're on the east coast of Australia). We run ~10:00am local time, which means the equivalent time in UTC is ~11pm the day before (eg. 10:00am 14/03/2024 in our local timezone is 11:00pm 13/03/2024). We receive our data with a date field only (no timestamp) as it's partially aggregated. So in my example above, we receive all data for 13/03/2024 around 9:30am on 14/03/2024. It looks like when the

volume_anomalies

test is looking at the

detection_period

, it's using the last completed UTC date, meaning it's testing against 12/03/2024, however we want to be looking at 13/03/2024. Any ideas on how to alter the timezone in elementary/dbt to match our schedule?