Automation rule not executing on trigger "Issue Created"

[chester.hansen@pillpack.com]

I have a Rule set up in a Service Desk that sets a custom field based on the request type and other criteria on issue creation. This rule has worked great since I created it 3 months ago and even after I updated it 14 days ago. But this morning at 5:52 AM it stopped executing. No configuration changed happened and its not running at all. The "Run as user" field is and has been the Automation for Jira User since the rule was created. This rule is crucial as it sets the custom field that is used to show the relevant issues in about 80% of the Service desk queues. 

I dont believe its due to an execution limit as our period just restarted two days ago and the rule scope is the single project.

Is there something obvious that I am missing?

[Liam Green · Accepted solution]

Hi chester.hansen@pillpack.com 

Welcome to the community!

Does the audit log show anything?

Regards, Liam

[chester.hansen@pillpack.com]

The last thing the audit log shows is the last time it executed at 5:52 AM. The same this is happening to other rules that use the issue created trigger.

[Liam Green]

Hi Chester

Looking at the Atlassian Status page, they are aware of this issue and are looking to resolve it now:

https://jira-service-desk.status.atlassian.com/

Regards, Liam

[chester.hansen@pillpack.com]

Thanks, It appears that is the issue.