TICKET HX-1289

Scheduled workflow didn't run last weekend

Status: Resolved Category: Workflows Priority: P3 Customer: Greg Holcomb (Northwoods Outfitters) Agent: Devon Park
Greg Holcomb Customer 2024-04-01 09:14 UTC

I have a workflow scheduled with cron `0 2 * * 6` — every Saturday at 2am. It didn't run last Saturday. Run history shows nothing for that day.

Devon Park Helix Support 2024-04-01 09:31 UTC

Hi Greg — checking. Your workflow is correctly configured and the trigger is enabled, but the schedule did fire as expected at 02:00 UTC on Saturday. Run was created and ran for 8 seconds before being marked succeeded. I see it in your run history.

Are you maybe looking at this in your local timezone? All Helix schedules run in UTC, so 02:00 UTC on Saturday is 22:00 Friday on the US East coast — the run would show under Friday's date if you're filtering by local time.

Greg Holcomb Customer 2024-04-01 09:38 UTC

Oh. Yeah I'm filtering by date and it's Friday in my view. So this is working as intended, I just had the wrong mental model. Is there a way to set it to run at my local 2am instead?

Devon Park Helix Support 2024-04-01 09:45 UTC

Helix doesn't currently support per-workflow timezones — schedules are UTC-only. To run at your local 2am (Eastern), you'd set the cron to `0 6 * * 6` for EST or `0 7 * * 6` for EDT. The downside is you'd need to update the cron when DST shifts, twice a year.

Most customers either accept the UTC schedule or set the workflow to fire when local time is between 2am-3am over the year (somewhere around 7am UTC).

Greg Holcomb Customer 2024-04-01 09:50 UTC

Cool — UTC is fine. Closing this out.

RESOLUTION

Workflow was actually running correctly. Customer was filtering run history by local timezone and the UTC schedule fire time fell on the previous day in their local time. No bug — confirmed run executed as expected. Educated customer that all schedules are UTC and DST is not handled.