Back to Workflows FAQs
HELP CENTER · FAQWorkflows2 min read

How should I handle daylight saving time in scheduled workflows?

A schedule tied to a local clock can behave differently when daylight saving time changes. Choose the intended timezone, inspect the next scheduled runs around clock changes, and avoid assuming that a local time always maps to the same UTC instant.

IaGenify
Workflows

Set the timezone intentionally

Use the timezone of the business event or audience, not whichever timezone happened to be active when the workflow was created. A local schedule follows that region's clock rules, which can shift its UTC execution time during seasonal transitions.

Some local times may be skipped or repeated when clocks change. Review how the scheduler handles those cases in the displayed schedule and history, especially for payments, reminders, and time-sensitive integrations.

Validate behavior before relying on it

Check upcoming run timestamps before a daylight-saving transition and again afterward. If an action must happen at an exact instant, consider scheduling against a fixed UTC time and documenting what that means for local users.

Test the workflow with a harmless action and review its run history after the change. Use idempotent steps or duplicate protection for jobs where a repeated local hour could otherwise process the same item twice.

Back to Workflows FAQs