My flows get skipped because of PendingWebhookSubscription error

[justinas_r]

Hi,

One of our flows stopped working - it skips the initial check with an error:

PendingWebhookSubscription. "The execution of the API notification recurring trigger 'Received_new_email' is skipped. Either the subscription registration is not yet complete or it is in an invalid state.

I can't find anything wrong with the flow - pushing the email manually completes the workflow with no errors. But a lot of emails get skipped because of this error. What does it mean?

[FCGALLEG]

Hi Justinas_r, 

Did you try to remove the connection and re-added it?

Please, let me know if it worked.

Thanks.

JAvier

[justinas_r]

Hi FCGALLEG,

Yes, I did try that, multiple times. Seems to make no difference.

[justinas_r]

Bump. This is a severe issue and our company needs a solution ASAP. We can't fix it ourselves because this error is not documented. Anyone from Microsoft? Please?

[FCGALLEG]

justinas_r,

Please, open a support case in order we can help you.

REgards,

Javier

[justinas_r]

 @FCGALLEG , how can I open a support case? Our company does not have a Premium plan, and without it, I am being redirected to the community page.

[SJacobs]

I am experiencing the a the following:

1) Trigger action "When a new email arrives (V3)" suddenly stopped working on July 31.  Had been working for months.

2) Run history - all runs: no activity since Jul 31

3) Run history - failed runs: found this error in the last successful run

4) Run history - Checks (no new data), about once per hour i get a "skipped" run.  Each one shows this in the trigger:

What's surprising and disappointing is that none of this appears as an error, you really need to go digging for it.   At this moment, I've reauthenticated using another connection, hoping this will solve the issue.  

[GTE]

I am noticing the same thing as what @SJacobs described. What's interesting is that I also had no activity since 7/31.

[Anonymous]

I have the same issue from the exact same date.

[SJacobs]

Update:  My flow is running again without issue.    Here's what I did:  I cleared connection to the trigger action "When a new email arrives (V3)" and then reapplied the same connection.  In the past hour the flow has successfully triggered twice.  I hope this helps others who experience this.

[Anonymous]

Update: Microsoft is currently experiencing a Service Degradation.

Details

Title: Flows containing office 365 triggers are failing to execute

User Impact: Flows containing office 365 triggers are failing to execute

More Info:

Not all flows are impacted by this issue, only flows using the “when an email arrives” trigger will be impacted.

Impacted flows can be found in the “checks” section of the flow maker portal.

Workaround:

If you have an impacted flow, disable and re-enable the flow in the maker portal to restore functionality.

Current Status: Following our investigation, we identified that this issue was caused by a previous flow connectors incident in which a recent deployment update to a portion of infrastructure responsible for routing traffic contained a misconfiguration that led to errors.

[SJacobs]

@Anonymous Where did you find your information?  I'd love to know where to search for notifications like this.  In fact, my first assumption that was that this was a known issue, but I couldn't find anything.  Thanks!

[Anonymous]

My company's ofiice 365 admin received an email with the service alert. The issue is currently being resolved.