Scheduled Flow configured for 22:00 but executing at 15:30 in PROD only

[cherlakolas]

Hi Team,
I'm seeing an unexpected behavior with a Scheduled Flow.

The flow is configured to run Weekly on Monday at 22:00, and both the instance timezone and user timezone are set to UTC.

In PROD, the actual sys_flow_context record shows the flow started at 15:30:04 UTC, even though the trigger is configured for 22:00 UTC.

In QA, the same flow configuration executes as expected, and the sys_flow_context record shows the flow started at 22:00:04 UTC.

I've already verified:

Trigger configuration is identical in QA and PROD.
Flow properties are identical in QA and PROD.
Execution times are being validated from the actual sys_flow_context records.

Has anyone encountered a similar issue where a Scheduled Flow executes at a different time than the configured trigger in one environment only?

Also, is there a backend table where the actual scheduler metadata or next run time for Flow Designer scheduled triggers can be verified?

[Hemanth M]

Hi @cherlakolas ,

1.I have heard of this issue - can you check who deployed this flow to Prod and what their  time zone (see if it matches).
2.can you try this to fix: make sure you profile set to the correct time zone and update the flow(deactivate  and activate in prod)
3 .verify the next run scheduled jobs.

Hope it helps!

[Tanushree Maiti]

Hi @cherlakolas 

Can you check and confirm Flow "Run As" by System user or User initiated session.

If it is User initiated session, what is his/her Time Zone - check and sys_user  table and confirm.

[Mehta]

Hi @cherlakolas , 

• The flow trigger time is based on the timezone of the user who sets the scheduled time, and even if the user changes their timezone later, it won't affect the trigger time.
• Flow Designer doesn't offer an option to set a specific timezone for the flow, so the trigger time is always determined by the timezone of the user who created it.
• If someone else modifies the trigger time and their timezone is set to EST, the trigger time and timezone will shift to EST.
• Please ensure your timezone is correctly set, then reset the scheduled trigger time, and it should trigger as expected.

The possible Solution is : 

1. Ensure the user's timezone is correctly set to the desired timezone for the flow execution.
2. Proceed to edit flow & activate when done
3. The scheduled trigger will be set to user's timezone

Check KB Article from Servicenow :  A flow with a scheduled trigger executed before scheduled time - Support and Troubleshooting

If my response helped, please mark it as correct and close the thread