Recurrence Fires at Wrong Time

[Brice235i]

Hello, I have built a recurring workflow that runs on a daily schedule.  Unfortunately there is a 38 minute daly with one of them, but for another there is a 2 hour 47 minute delay.  and for another 2 hour 49 minute delay. Doesn't make any sense.  I've attached the recurrence action and a sample of run times for each. Appreciate your ideas thank you.

[AlanPs1]

Hi @Brice235i 

I am not certain this will be the complete fix as I am in a UTC time zone (UK) but this should be worth a try.

Set a "start time".

This post explains this - https://powerusers.microsoft.com/t5/Using-Flows/Recurrence-set-for-10-but-ran-at-9-22/m-p/241400

If nothing else, it will get your Flows running consecutively on the hour if per say you set to suit tomorrow:

2019-03-09T14:00:00Z

The above is relevant to the first image, and will run at 2pm. Change to suit for your other Flows.

This may be enough so give it a try, any issues, post back and we can go from there if still a delay.

If you have found my post helpful, please mark thumbs up.

If this post has solved your problem, please click "Accept as Solution".

Any other questions, just ask.

Thanks, Alan

[Brice235i]

Thank you Alan, I will give this a go and accept solution if it works.

[Brice235i]

Hi Alan, it didn't work.  Trying again though as maybe I entered the start time incorrectly.  Interestingly the parameters don't seem to stick.  I enter the timezone and start time, save the workflow.  I go back in to edit and the parameters do not appear.  When I go to re-add the value I added is remembered though.. weird.

Hopefully tomorrow at 2pm I will receive the workflow email.  

[AlanPs1 · Accepted solution]

Hi. As a simple test. Please start a new Flow with a 5 min recurrence and a simple compose action with any value in it. Observe it for a couple of runs and switch it off after.

Make sure this Flow has the correct start time and let me know how that performs please.

Thanks, Alan

[Brice235i]

Thank you Alan, going home for the day.  Will do this tomorrow.  Thanks again.

[Brice235i · Accepted solution]

Hi Alan, the solution almost correct... except for one thing..

2019-03-09T14:00:00Z

This still did not work....  Somewhere else I read to remove the 'Z' on the end.  Now it works... The Z only for UTC time.  I didn't know that!  Thanks again.

[AlanPs1]

Hi @Brice235i .

Thank you for coming back with that update, I have also marked your reply as the solution as this has required both our input to resolve.

I wasn't aware the "Z" coming off the end would work, perhaps for non UTC areas so with both our replies, and both our solutions this presents a decent answer for anyone who will look again in the future!

#Kudos to you and Happy Flowing!

Thansk, Alan

[Brice235i]

Thanks Alan, I have never heard of this before!  This is what I found:

"The UTC time zone is sometimes denoted by the letter Z – a reference to the equivalent nautical time zone (GMT), which has been denoted by a Z since about 1950. The letter also refers to the "zone description" of zero hours, which has been used since 1920 (see time zone history). Since the NATO phonetic alphabet and amateur radio word for Z is "Zulu", UTC is sometimes known as Zulu time. This is especially true in aviation, where Zulu is the universal standard. This ensures all pilots regardless of location are using the same 24-hour clock, thus avoiding confusion when flying between time zones."