How to investigate delays in automation rules?

[Craig Easton]

My automation rules that are scheduled to run on issue creation are taking 10+ mins to run. This issue has just started. The baffling part to me is that this automation is multi-project, on 1 project it's instant but on another it's delayed.

How do I start to investigate the root cause?

[Bill Sheboy · Accepted solution]

Hi @Craig Easton 

First thing: would you please post images of your rule and the audit log details showing executions which run as expected and others which do not?  That may provide some context for the community to offer ideas.  Thanks!

Next, what is your Jira license level: free, standard, premium, etc.?  There are limits to the number of executions for global/multi-project rules...by license level.

Finally, when you and your site admin look at the global audit log, performance insights/measures, what do you observe?  For example, is there any throttling or high numbers of rule failures?

Kind regards,
Bill

[Craig Easton]

@Bill SheboyIt seems the issue is gone. It was happening for ~2 hours this morning. I will note your tips for the next time the issue appears (hopefully never).

[Bill Sheboy]

I am glad to learn that it is gone now.

For early warning, I recommend creating a global automation rule which monitors / triggers on the service limits / usage of your instance, and have it email the site admin when limits are about to be exceeded: 

https://support.atlassian.com/cloud-automation/docs/jira-automation-triggers/#Service-limit-breached

https://support.atlassian.com/cloud-automation/docs/automation-service-limits/