Newly installed Automation for Jira - Data Center and Server does not work
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
Summary
In very rare cases, after performing a brand new installation of Automation for Jira, the plugin would not work:
Newly created automation rules might not execute, or
Errors will be presented when creating the rules
Environment
Jira 8.x, Automation for Jira 7.3 and above
Diagnosis
In the application logs under $JIRA_HOME/logs/atlassian-jira.log* will display entries like below. This is not limited to AO_589059_AUTOMATION_QUEUE, but can occur for other AO_589059* tables too.
1
2
3
4
5
6
7
8
2021-12-02 13:21:47,352+1300 automation-event-serializer:thread-1 ERROR username 24x1632749x1 6r2zx5 172.16.41.38 /secure/WorkflowUIDispatcher.jspa [c.c.j.p.a.service.execution.JiraThreadLocalExecutor] Unexpected error in thread local executor with actorKey 'JIRAUSER13705'.
com.querydsl.core.QueryException: Caught SQLServerException for insert into "jiraschema"."AO_589059_AUTOMATION_QUEUE" ("CLAIM_COUNT", "CLIENT_KEY", "CREATED", "PAYLOAD", "PRIORITY", "EXECUTION_UUID")
values (?, ?, ?, ?, ?, ?)
...
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.base/java.lang.Thread.run(Unknown Source)
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid column name 'EXECUTION_UUID'.All AO_589059* tables are from the Automation for Jira plugin. We need to verify if the errored entries have been there before Automation for Jira was installed.
Check if there is a significant number of entries present in the below-listed tables that are used by Automation for the Jira add-on. You may need to engage your DBA to help with a variation of select count(*) from <tablename> to match your database.
AO_589059_AUTOMATION_QUEUE
AO_589059_AUDIT_ITEM_PROJECT
AO_589059_AUDIT_ITEM_ASC_ITEM
AO_589059_AUDIT_ITEM_CGE_ITEM
AO_589059_AUDIT_ITEM_COMP_CGE
AO_589059_AUDIT_ITEM
AO_589059_RULE_STAT
AO_589059_RULE_STAT_ROLLUP_DAY
AO_589059_RULE_STAT_ROLLUP_HR
AO_589059_RULE_STAT_ROLLUP_MIN
If you have just installed the add-on and created one automation rule as a test, you shouldn't be seeing a significant number of entries in these tables.
Some of the existing entries would have been added after installing and configuring the add-on. However, it is likely that other records would be from a time when the add-on was trialed long ago or when the Lite version of the add-on was being used.
To help confirm this, refer to a copy of your Jira instance's database from before the Automation for Jira was installed (ideally if you have a Production or UAT environment where the add-on has not YET been installed). Perform the select count(*) from <tablename> of the same tables to confirm whether there have been existing entries in those tables prior to installing Automation for Jira.
Cause
The behaviour is most likely because a trial or Lite version of the add-on was used in the past.
As a result, even on an allegedly brand new installation of the add-on, the add-on will attempt to upgrade the existing data in the Automation for Jira tables that was generated there before, and will run into the issue documented by this linked article
Solution
There are two options at this point:
If you would like to keep the data from the previous Automation for Jira installation, follow the steps from the article linked in the 'Cause' section above.
If it's genuinely a brand new installation of Automation for Jira add-on, you could follow these steps:
1) Uninstall Automation for Jira add-on
2) Stop Jira (on all cluster nodes if it's a Jira Data Center cluster)
3) Delete (drop) the above-mentioned tables from the Jira database (you may need to engage your DBA to assist with this)
4) Start Jira
5) Install Automation for Jira add-on from scratch
Was this helpful?