Unanswered

Scheduled flow with recurrence trigger not starting at correct time

(0) Share

Report

Posted on by CL-30051855-0

Howdy,

I was wondering if anyone here had experience with an issue my organization is running into with a couple of Power Automate flows that are not starting at the selected recurrence time used in the workflow trigger. Here is the issue. We have created two workflows, both workflows have a "Recurrence" trigger set for 8:00AM PST. The workflows trigger successfully each morning and have a short total run time. However, for some reason neither flow actually starts at 8:00AM, one of them seems to trigger at 8:40AM and the other at 8:45AM.

Is there some external factor that is delaying the workflows from kicking off at the correct time? I was wondering if there was some sort of Power Automate job queue, but even if there was it does not seem like my org couple possibly have enough concurrent flows running at 8:00AM to cause 40+ minute delays. I thought that maybe it had something to do with daylight savings in PST, but that seems like it would throw the flows off an hour either direction, instead of just 40 - 45 minutes.

Flow A Trigger:

Flow A Start & Run Times:

Flow B Trigger:

Blow B Start & Run Times:

Thank you for your time!

Chris

Categories:

General topics

I have the same question (0)

All responses (3)

Answers (0)

lbendlin 8,649 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

We see that frequently when the service is very busy due to other activities. Check your admin console for the total number of flows per day/hour etc.

The documentation specifically avoids any mention of a SLA.

Was this reply helpful? Yes No
shravanreddy13 30 on at

Like (2)

Report
Copy link

Link copied!

From a community reference (non-Microsoft but aligning with official docs):

“Microsoft will do this to load‑level the requests of customers that all have schedules specified. Otherwise, there will be a large spike of traffic … only the hours are configured. So, if we specify 12 (for example), we may assume it will run at 12 pm. But it doesn’t necessarily mean that. What it means is that will run during the 12th hour, sometime between 12 pm and 12 :59 pm.”

Try to explicitly set the minutes in the “At these minutes” field of your trigger:

Setting it to 0 ensures the flow aims to fire at 00 minutes past the hour (e.g. 8:00 AM), rather than any random time within that hour.

Was this reply helpful? Yes No
CL-30051855-0 4 on at

Like (0)

Report
Copy link

Link copied!

@shravanreddy13, I will give this a try. Yesterday I had moved the run times to 7:30AM and they ran exactly at that time, so I think you may be onto something with needing to set the minutes to ensure the exact run time.

@lbendlin, I was trying to check the flow run records in the "Automation Center" to see if the flow was being delayed, but unfortunately it looks like only flows that are in solutions show up here, and we had not added these two flows to a solution yet. However, looking at the 8:00AM start time, it does not seem like there is too much concurrent traffic occurring.

Thanks!

Chris

Was this reply helpful? Yes No