The flow is not being triggered by the Microsoft Forms submit event.

[KKG]

Dear Community, good day,

Today i found the flow has not been triggered by Microsoft Form submit event. The set up is as follows

Today occurred at least 9 Form submit events + one manual trigger test.

The Form itself does the job - all summited data saved properly.

Latest successful automatic run of the flow was yesterday. Please see latest activity log.

Cloud services in my region - available. (https://status.azure.com/en-gb/status)

Does any one have an issue? How to handle it? 

PS: Performed test on another pair Form-Automate Flow - with same result, i.e. flow doesn't trigger on form submit. Seems the event signal is lost somewhere on route between Microsoft Form - Automate Flow.

[MBates]

Same since the beginning of this week.

[natg · Accepted solution]

I've had the same issue since February 13th. Here's another thread that suggests turning the flow off and on again will fix. It didn't work for me though. 

https://techcommunity.microsoft.com/t5/microsoft-forms/new-form-submissions-not-pulling-to-power-aut...

[hoangja]

I was also experiencing this issue, beginning on 2/15.
Thankfully your solution for turning the flow off and on worked for me!

[KKG]

Thanks indeed.

Somehow, prior i got your reply, intuitively i turned the flow off and on again and it did the trick. The flow resumed its' normal behavior. 

However, this is to accept your solution. 

[dhu79]

I was seeing this as of 2/13 as well. The turn off then back on appeared to work. Is there a way to detect when this occurs? To receive a notification? Thank you!

[DDCJOEE]

I've also been seeing this, as well as another issue where one of my forms can no longer retrieve responses in Power Automate. I really wish there was better monitoring we could set in place for these kinds of flows. I build a lot of form to case processing flows for my company, where our customers will out a form, and the flow generates a Salesforce case. Many of these cases operate on tight deadlines. This issue could start resulting in SLA fines for us even after just a few hours of the flow not running, so it's critical for me to be able to identify any issues like this, report them to my stakeholders, and resolve ASAP.

[MBates]

Agreed.  My current thought is to create a flow that would run hourly.  The flow would count the number of a particular Form received over the past hour and compare that with the number of Flows ran for that Form.  If equal, do nothing.  If not equal, send an email reporting the discrepancy.

[DDCJOEE]

That is a great idea. I'll try building something like that later today. Thanks!