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!

[cherlakolas]

Thanks, @Hemanth M .

I checked the timezone of the user who promoted the flow to PROD, and it doesn't appear to align with the 22:00 → 16:30 conversion.

I also found a difference in the underlying sys_flow_timer_trigger record:

QA timer trigger = 22:00
PROD timer trigger = 16:30

Flow Designer shows 22:00 in both environments, so the timer trigger record in PROD appears to be out of sync with the Flow Designer configuration.

Have you come across a scenario where the sys_flow_timer_trigger record differs from the Flow Designer schedule? Would republishing/reactivating the flow regenerate and synchronize the timer trigger record?

[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.

[cherlakolas]

Hi @Tanushree Maiti, Thanks for checking, yes flow uses run as "System User" only