Microsoft Sentinel
A scalable, cloud-native solution for security information event management and security orchestration automated response. Previously known as Azure Sentinel.
1,241 questions
Could not trigger playbook: xxx . An internal server error occurred. Please contact support for assistance.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(83.2, 31%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EVC%3C/text%3E%3C/svg%3E)
Vojtěch Mikeška
0
Reputation points
Dear team,
We are facing a problem with triggering a rule in sentinel. In sentinel we have a rule set to incident updated -> run playbook. As of 2:00 am this morning the automation rule is unable to run the playbook. The error that is seen in the log is: Could not trigger playbook: {{playbook.name}}. An internal server error occurred. Please contact support for assistance. No changes were made to this rule. We have these automation rules in 3 production subscriptions and this problem occurs in two of them. At the same time, it occurs in our test subscription - where the test playbook is run (same schema as the production one).
Manually run playbook on incident is possible - there is no any problem.
Sign in to answer