Another playbook issue

%3CLINGO-SUB%20id%3D%22lingo-sub-1095236%22%20slang%3D%22en-US%22%3EAnother%20playbook%20issue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1095236%22%20slang%3D%22en-US%22%3E%3CP%3EAs%20of%20Sunday%2C%20the%20previous%20issue%20of%20the%20playbooks%20not%20running%20was%20mitigated%20and%20all%20had%20returned%20to%20normal%20functionality.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EToday%2C%20a%20new%20issue%20arose.%20Alerts%20are%20triggering%20on%20all%20of%20the%20playbooks%20that%20are%20currently%20enabled.%26nbsp%3BNo%20errors%20found%20within%20the%20playbooks.%20All%20playbooks%20are%20assigned%20properly.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnyone%20else%20experiencing%20this%20issue%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1095263%22%20slang%3D%22en-US%22%3ERe%3A%20Another%20playbook%20issue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1095263%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F418279%22%20target%3D%22_blank%22%3E%40leoszalkowski%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20now%20the%20opposite%20of%20the%20previous%20issue%2C%20that%20is%20thousands%20of%20playbook%20triggers%20for%20a%20handful%20of%20alerts.%20For%20one%20alert%20I%20may%20get%20100%20runs%20of%20the%20same%20playbook%2C%20in%20matter%20of%20seconds.%20Since%20I%20have%20email%20notifications%20as%20part%20of%20the%20playbook%2C%20my%20mailbox%20is%20being%20flooded%20with%20emails.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1095277%22%20slang%3D%22en-US%22%3ERe%3A%20Another%20playbook%20issue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1095277%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F353788%22%20target%3D%22_blank%22%3E%40AdiGrio%3C%2FA%3E%26nbsp%3BYup.%20We%20have%20email%20notifications%2C%20Teams%20notifications%2C%20and%20others.%20All%20getting%20flooded.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20going%20to%20disable%20my%20playbooks%20for%20the%20time%20being.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1097538%22%20slang%3D%22en-US%22%3ERe%3A%20Another%20playbook%20issue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1097538%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F353788%22%20target%3D%22_blank%22%3E%40AdiGrio%3C%2FA%3E%26nbsp%3BIdentical%20messages%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1097790%22%20slang%3D%22en-US%22%3ERe%3A%20Another%20playbook%20issue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1097790%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F46875%22%20target%3D%22_blank%22%3E%40Gary%20Bushey%3C%2FA%3E%26nbsp%3BYes%2C%20identical%20messages%20as%20it%20appeared%20that%20for%20each%20alert%20triggered%2C%20the%20associated%20playbook%20would%20be%20executed%20several%20times.%20I%20had%20over%201000%20playbook%20runs%20for%2020-30%20alerts.%20Removing%20and%20reassigning%20the%20playbook%20seemed%20to%20fix%20the%20problem%20(though%20I%20realized%20that%20late)%2C%20very%20similar%20with%20the%20situation%20several%20days%20ago%2C%20when%20no%20playbooks%20were%20executed%20for%20alerts%20but%20worked%20after%20removing%20and%20reassigning%20the%20playbook.%20My%20guess%20is%20that%20the%20two%20problems%20are%20related.%20The%20problem%20was%20fixed%20sometimes%26nbsp%3B%20yesterday.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Contributor

As of Sunday, the previous issue of the playbooks not running was mitigated and all had returned to normal functionality.

 

Today, a new issue arose. Alerts are triggering on all of the playbooks that are currently enabled. No errors found within the playbooks. All playbooks are assigned properly.

 

Anyone else experiencing this issue?

 

 

4 Replies
Highlighted

@leoszalkowski 

 

I have now the opposite of the previous issue, that is thousands of playbook triggers for a handful of alerts. For one alert I may get 100 runs of the same playbook, in matter of seconds. Since I have email notifications as part of the playbook, my mailbox is being flooded with emails. 

Highlighted

@AdiGrio Yup. We have email notifications, Teams notifications, and others. All getting flooded. 

 

I'm going to disable my playbooks for the time being.

Highlighted

@AdiGrio Identical messages?

Highlighted

@Gary Bushey Yes, identical messages as it appeared that for each alert triggered, the associated playbook would be executed several times. I had over 1000 playbook runs for 20-30 alerts. Removing and reassigning the playbook seemed to fix the problem (though I realized that late), very similar with the situation several days ago, when no playbooks were executed for alerts but worked after removing and reassigning the playbook. My guess is that the two problems are related. The problem was fixed sometimes  yesterday.