Flow not triggered

[hanruhao]

Hi All

I am in Sydney and I find both of my flows are not triggered. The flow is supposed to be triggered when a new entry in the Microsoft Forms. But there are 15 + submissions just happened in past 30 mins , but none of them are triggered in the Microsoft Flow. Is there a service interruption at the moment?

Regards

[Sastro_Chang]

Hello,

@han Any solution so far?

[AndrewGibson1]

Hi there,

Yes this all seems to be working now - I guess Microsoft worked it out!

[hanruhao]

I think the  submission to my form happened yesterday 12:45PM to 4:30 PM are not triggered. I have to manually run the process for those entries. any entries happened after 4:30pm can trigger the flow.

[jvargas33]

@hanruhao by any chance has Microsoft reached out to you regarding a root cause or how this issue was solved on their end?

[hanruhao · Accepted solution]

The Root Cause is that . There was an Azure Service Bus outage on 8/31. The impact started at ~8/31 02:00 UTC, ended at ~8/31 06:00 UTC.

There is a manual way to trigger the untriggered the submission. you have to replicate your current flow. Replace the trigger to "Manually trigger a flow", add a number input. This number will be your form submission ID.

[Sastro_Chang]

Thanks @hanruhao 

[GarciaMcgC]

I'm having this same issue since yesterday. Two separate flows triggered by an MS Forms submission are not started after a number of forms have been submitting. No activity, no errors on either side after the forms were submitted. Any answers?

[JamesThompson]

Yep, same here.  As of this morning, Power Automate is not triggering from any Form submissions.

[trad]

Same issue here.

[KenWen]

Same issue here but with a weird twist. Flows are triggered when I submit the form but not when other users submit the form.

The flow was created by me and is in my personal flows.  The form is a group form. This has been working for months and suddenly started showing this weird behaviour.

Will changing this flow to a group flow help? Has anyone else experienced this??

[KenWen]

Thank you. I copied my flow into a new flow by doing "Save As". Do you know or does anyone know how to convert my flow from automate flow to manual flow?

[KenWen]

This looks like a Microsoft issue: https://emea.flow.microsoft.com/en-us/support/

"Error: Since Thursday, December 3, 2020, at 3:35 PM UTC, there was degradation in Microsoft Forms so some flows with Microsoft Forms triggers are not triggering on form submissions. Engineers in Forms and Power Automate are actively mitigating the issue."

[KenWen]

Looks like Microsoft has fixed this. I just tested and it is working again! 🙂 🙂 

Warning: From Thursday, December 3, 2020, at 3:35 PM UTC until 20:00 UTC, there was degradation in Microsoft Forms in East US that caused Power Automate flows that trigger on forms rooted in East US to not trigger on form submissions during the impact time period. The root issue in Microsoft Forms has been mitigated as of 20:00 UTC.

[hanruhao]

For the form submissions have missed. you can record their form ID.  Then copy your current flow. remove the current Trigger to Manually trigger a Flow. Make the input value either single integer or array. Then you can manually trigger the missed submissions.

[hubertlam]

Happening again today - some form submissions not being picked up by Flow. 

[Anonymous]

Flagging that this might be happening again in 2023. No submissions have triggered flows since the morning of 15/2/2023.

[Heather_Hare]

I agree. It's frustratingly inconsistent, too. I think we'll be moving to a new platform soon. 

[Anonymous]

Same. We have had several workflows fail to trigger since 2/14/2023

[hanruhao]

We had this issue happen to one of the user-created flows around last Friday as well.    But we recreated the flow in the same account it works again.  It may be related to the license.  All the flows created in another licensed account works no issues last week.

[Anonymous]

I raised a support ticket and got confirmation from Microsoft that there was an issue with the form trigger experienced on 15/02/2023. All seems to be working normally now (17/02/2023).