- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi All,
I have one small query, I need to activate the record producer on October 19th 12:00AM and the same should deactivate on October 31st 12:00AM on France/Paris time zone.
In the flow properties, I have used Run As as System user, Could you please check the screenshots attached and confirm this flow will trigger exactly at the mentioned dates or any change is required.
Currently, i have scheduled the flows based on UTC time zone and the screenshot shows the flow will trigger on October 19th 12:00AM France/Paris time zone and also the other screenshot shows the flow will trigger on October 31st 12:00AM France/Paris time zone..
Should I follow the UTC timezone or as per my profile US/Eastern time zone? Please suggest
Could you please check and confirm.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi ,
Your UTC math is right. Paris is UTC+2 on Oct 19 and UTC+1 on Oct 31, because daylight saving ends on Oct 25. That gives:
- Oct 19, 12:00 AM Paris = Oct 18, 22:00 UTC
- Oct 31, 12:00 AM Paris = Oct 30, 23:00 UTC
The catch is that the Run Once trigger has no time zone field. The time you enter is taken in the time zone of the user who saves the trigger, not UTC and not the Run As user. Run As (System User) only controls the execution context.
So the screenshots only prove the flow fires at the right time if the saving user’s profile is UTC. With your profile on US/Eastern, 22:00 means 22:00 Eastern, which is 04:00 Paris on Oct 19, so it would fire late.
Suggested fix:
- Set the time zone on your user profile to Europe/Paris (or use a user who already has it).
- Open both flows, set Run Once to 12:00 AM on 2026-10-19 and 12:00 AM on 2026-10-31, then save and activate.
- Check the trigger record in sys_trigger (System Scheduler > Scheduled Jobs, search by flow name). Next action should show 2026-10-18 22:00 UTC and 2026-10-30 23:00 UTC.
- Make sure nobody re-saves the flows from a different time zone later, because that can change the trigger time.
Because the run time is stored as a time of day, it can shift by one hour around daylight saving changes. Please confirm the Next action value after saving, and test in a sub-prod instance first if you can.
If this helped to answer your query, please mark it helpful & accept the solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi ,
Your UTC math is right. Paris is UTC+2 on Oct 19 and UTC+1 on Oct 31, because daylight saving ends on Oct 25. That gives:
- Oct 19, 12:00 AM Paris = Oct 18, 22:00 UTC
- Oct 31, 12:00 AM Paris = Oct 30, 23:00 UTC
The catch is that the Run Once trigger has no time zone field. The time you enter is taken in the time zone of the user who saves the trigger, not UTC and not the Run As user. Run As (System User) only controls the execution context.
So the screenshots only prove the flow fires at the right time if the saving user’s profile is UTC. With your profile on US/Eastern, 22:00 means 22:00 Eastern, which is 04:00 Paris on Oct 19, so it would fire late.
Suggested fix:
- Set the time zone on your user profile to Europe/Paris (or use a user who already has it).
- Open both flows, set Run Once to 12:00 AM on 2026-10-19 and 12:00 AM on 2026-10-31, then save and activate.
- Check the trigger record in sys_trigger (System Scheduler > Scheduled Jobs, search by flow name). Next action should show 2026-10-18 22:00 UTC and 2026-10-30 23:00 UTC.
- Make sure nobody re-saves the flows from a different time zone later, because that can change the trigger time.
Because the run time is stored as a time of day, it can shift by one hour around daylight saving changes. Please confirm the Next action value after saving, and test in a sub-prod instance first if you can.
If this helped to answer your query, please mark it helpful & accept the solution.
