I have a flow that is triggered when a Dynamics record is created or updated, but it either takes absolutely ages to trigger (20+ mins), when it says it should take 1 minute, or it doesn't trigger until I go to the flow and turn it off and back on again.
I had the same for another flow that was supposed to be triggered at 5pm last night, when I checked it at 18:30, it hadn't run, turned it off and back on and it ran straight away (even though it was way past 5pm) so what is happening here, why are my flows not starting, and why does the trigger seem to be cached somewhere until I turn the flow off and back on?
This unreliability makes it very difficult to demonstrate it's potential to any senior members of staff.
Solved! Go to Solution.
Hi @ NickDewitt,
Have your problem still exists?
Could you please share a screenshot of your flows which couldn't be triggered normally?
My flow always be triggered normal and don't have the issue that you mentioned.
For your first flow, would the flow takes absolutely 20+ minutes to trigger,or would trigger until you go to the flow and turn it off and back on again?
What browser are you use when the flow don't normally trigger?
Could you please check if you have a normal network status?
Pleaseshare more details so we could provide a proper workaround for you.
Please let me know if your problem could be solved.
Thanks for your response, it seems to be better this morning.
I did notice that I didn't set the time-zone for the scheduled Flow, it was scheduled to run at 17:00 and has run at 18:37 every day - incidentally the same time I had turned it off and on again last week.
The dynamics created or updated trigger was definitely running extremely slowly last week and taking up to and even over an hour to trigger, and some of the updates did not seem to be triggering at all.
I have a Powerapps P2 license with my Dynamics 365 package, but I did notice I had a total of 13 different Flow and PowerApps licenses assigned to me from various Office 365 and Dynamics 365 packages, including a PowerApps and Flow P2 trial. I disabled that license last week, so i'm wondering whether I was getting throttled as the trial license was taking precedence for some reason?
Also, the dynamics instance that I am testing on is the free sandbox version, not sure if that should make a difference.
Is there any way to find out the reason for flows taking a long time to start?
I am using the latest version of Chrome as as browser, our network activity is normal, and the trigger is running on a Dynamics 365 instance so it's all running in the MS cloud, my network activity shouldn't matter for the trigger, I am crossing the on-premise gateway inside the flow, but as soon as it triggers the response from my Web API is immediate.
Have you had a chance to apply @v-yuazh-msft‘s recommendation to adapt your Flow? If yes, and you find that solution to be satisfactory, please go ahead and click “Accept as Solution” so that this thread will be marked for other users to easily identify!
Thank you for being an active member of the Flow Community!
Flow Community Manager
Hi @GabrielStJohn I didn't see any recommendation to adapt my Flow in that response, just a request for more info which I provided.
My Flows from dynamics seem to be more responsive at the moment, but I need to find some time to do more testing to ensure that it is triggering in a timely manner.
My scheduled Flow is still running 36 minutes later than scheduled every day though, even though I have set the correct time zone.
Do you set the flow run at 17:00 in your flow?
The trigger "Recurrence" trigger would run the flow with the time that you scheduled with UTC time.
However, the scheduled time in the "Recurrence" trigger could only support the UTC time and schedule a flow with a local time is not supported in microsoft flow currently.
All times in Microsoft Flow are in Universal Time by default
You could refer to link below to know the UTC time now:
Yes, it's set for 17:00, and the Time Zone is set to UTC+00:00 - It definitely seems to be supported to select a Time Zone in the Recurrence trigger according to the UI that comes with it, and it did start running an hour earlier when I selected the correct time zone.
Granted as we are on British Summer Time right now, we are an hour ahead, but then I would expect it to run an hour earlier, not 35 minutes late.
Thank you for the help, it's much appreciated.
What is the solution to the flow not getting triggered (not the recurring flow)?
I am facing similar issue.
When I am in the test mode of the flow, it triggers immediately, but outside test mode, it is not getting triggered unless I do a blank edit and save of the flow.
Please help as this is blocking our design.
I am having a similar problem.
I wrote a flow which is triggered by a recurrent schedule and refers to dates on an excel file domiciled on Sharepoint for it to run.
I have tested it and its fine whenever tested. However, it always sends a reminder a day late after the scheduled dates, and sometime when i go back to edit or tweak the excel document, it fails to pick the dates and sometime it wont even trigger at all. Keeping in mind that I have implemented all that was said earlier in this thread.
I was almost inviting the execs after the test was successful only for it to send the reminder late.
Can someone please help
See the latest Power Automate innovations, updates, and demos from the Microsoft Business Applications Launch Event.
Find your favorite faces from the community presenting at the Power Platform Community Conference!
Check out the announcement of Power Platform content at Microsoft Ignite!
Features releasing from October 2020 through March 2021