I was trying to set up a scheduled flow to run in my timezone currently standard time (GMT +11) - The dropdown to select my timezone shows the daylight savings time GMT +10
Not sure if this effects anything
Would be nice if this was timezone aware.
Topic summary
A user encountered confusion when setting up a scheduled Flow, noticing the timezone dropdown displayed GMT+10 (daylight savings time) instead of the expected GMT+11 (standard time) for their location.
Clarification provided:
- GMT offset values in the dropdown don’t adjust for daylight savings time—this is part of the standard convention
- The displayed GMT offset may appear incorrect (e.g., showing +4 when actually running 5 hours off current GMT)
Resolution:
- Flows automatically account for daylight savings when a specific location-based timezone is selected
- Users should ignore the GMT label and trust that the system will execute at the correct local time
- The issue is cosmetic rather than functional—scheduled Flows will run at the intended time despite the potentially misleading GMT offset display
Hi I think you mean daylight savings aware. It should be that as well but possible there is some defect. We’ll investigate.
I got a clarification on this - the GMT values don’t actually change for daylight savings time, which is confusing but part of the standard. So it may so +4 when it’s actually running 5 hours off the current GMT time.
In summary: if you choose a timezone at a particular location, it will run factoring in daylight savings time and just ignore the GMT label.
1 Like
Very interesting, thanks for the clarification