Automation Rules admin page is broken and displays a template error in Jira

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

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible


The global Automation Rules admin page displays a template error and it's not possible to use it or even see the automation rules.

Example error:

Error in global automation page "Sorry we had some technical problems during your last operations"


Upon accessing the Automation Rule admin screen, a template error is exhibited like:

1 In 'print' tag, expression "$localeString" evaluates to undefined.

And in the atlassian-jira.log, prior to this error, there's a SQL error:

1 2 3 4 5 6 2021-03-17 18:07:01,345 http-nio-8080-exec-27 ERROR admin 869x15542657x3 13rfhg7 /secure/AutomationGlobalAdminAction!iframe.jspa [c.c.j.p.a.web.admin.AutomationGlobalAdminAction] Unexpected error loading global automation UI: com.querydsl.core.QueryException: Caught SQLServerException for select "AO_589059_RULE_STATE_LATEST"."CURRENT_AUDIT_ID", "AO_589059_RULE_STATE_LATEST"."CURRENT_CATEGORY", "AO_589059_RULE_STATE_LATEST"."CURRENT_CREATED", "AO_589059_RULE_STATE_LATEST"."ID", "AO_589059_RULE_STATE_LATEST"."PREVIOUS_AUDIT_ID", "AO_589059_RULE_STATE_LATEST"."PREVIOUS_CATEGORY", "AO_589059_RULE_STATE_LATEST"."PREVIOUS_CREATED", "AO_589059_RULE_STATE_LATEST"."RULE_ID", "AO_589059_RULE_STATE_LATEST"."EXEC_COUNT" from "dbo"."AO_589059_RULE_STATE_LATEST" "AO_589059_RULE_STATE_LATEST" where "AO_589059_RULE_STATE_LATEST"."RULE_ID" in (?, ?, ?, ?, ........,?) ... Caused by: The incoming request has too many parameters. The server supports a maximum of 2100 parameters. Reduce the number of parameters and resend the request.


This issue is caused because Automation for Jira queries the database passing every Automation Rule ID as a parameter when building the admin screen. MS SQL Server has a limit of 2100 query parameters so when there are more than 2100 Automation Rules the admin screen breaks.

Automation Rules continue to run unhindered — it's "just" the admin screen that breaks.

JIRAAUTOSERVER-241 - [Creating more than 2100 Automation Rules with MS SQL breaks the Automation admin screen, Status: "CLOSED"]


Until JIRAAUTOSERVER-241 is fixed and Automation for Jira's updated to a fixed version in your instance, the only solution is to workaround it by deleting some Automation Rules directly on the database.

This KB on How to manually delete an Automation Rule on the database in Jira offers the step-by-step to accomplish that. You should delete enough rules so they count less than 2100:

1 select count(*) from "AO_589059_RULE_CONFIG";

Updated on June 11, 2024

Still need help?

The Atlassian Community is here for you.