Issue Summary

Automation execution fail due to JQL evaluation in the rule trigger timing out.

Latest investigation notes:

When Automation calls Jira to perform JQL evaluation, the downstream service took a long time to hydrate the results involving SLA custom fields. This exceeds the timeout in Automation and thus the error. This issue is more evident when the JQL matched many work items and the space has many SLAs configured in it.

Steps to Reproduce

1. Create an Automation rule that runs on a schedule with JQL filtering
2. Set up multiple SLA configurations on the space and multiple work items that matches the JQL set up in the Automation trigger
3. Run the Automation

Expected Results

The Automation rule runs as normal

Actual Results

The execution failed with the following error in the Audit log:

Jira was slow to respond, because the JQL query returned too many issues. Narrow the scope of this JQL query and try again: 

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available.