Scheduled flow runs twice or not at all on DST switch
Tools handle DST differently. Plan in UTC and convert only at output.
Try this first
- 1Set all schedules explicitly in UTC or Europe/Amsterdam
- 2Avoid 02:00-03:00 as run time
- 3Test around DST shift (last Sunday March and October)
- 4Log start time in both UTC and local
When to bring us in
Cross-timezone teams: standardize on UTC for all scheduled work.
See also
- n8n: self-host or cloud?Self-hosted is cheaper at volume and keeps data local. Cloud removes ops burden.
- Zapier or Make: which fits better?Zapier is straight-line; Make handles complex flows with routers and iterators for less money.
- Power Automate Cloud or Desktop: which to use?Cloud for SaaS integrations and triggers. Desktop for RPA against legacy Windows apps without APIs.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.