Automation fails with error "Jira was slow to respond, because the JQL query returned too many issues."

Platform Notice: Cloud Only - This article only applies to Atlassian products on the cloud platform.

Summary

Scheduled Automation rules failing with errors:

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

resolution = Unresolved AND updated <= -7d AND assignee is not EMPTY AND status = "Backlog"

These are Global automation rules. The rule generally works fine when scope is - (Manual projects)

However, the rule fails when the scope is - Project categories (Service or Software) / Global.

Environment

Jira Service Management Cloud

Diagnosis

  • Manually running the Automation rule might fail ortake longer (~60 seconds) to execute. 

  • HAR file captured while running the Automation manually will have below 400 errors and "jqlTooComplex" response:

    • 1 2 3 4 Request URL:https://<URL>/secure/QueryComponent!Jql.jspa Request Method:POST Status Code:400 Remote Address:<IPAddress>
    • 1 2 3 4 5 6 { "errorMessages": [ "jqlTooComplex" ], "errors": {} }

Cause

  • Try accessing Application link within the site you run into the error "Something went wrong. The server returned a bad response."

  • Verify the invalid or corrupted Application links to Jira application that you might have.

Solution

Remove or re-add the corrupted application link.

Updated on March 4, 2025

Still need help?

The Atlassian Community is here for you.