Automation for Jira - Rules are not triggered for some Jira issues due the application being disabled

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


Automation rules are not triggered for some Jira issues (Jira issues are randomly skipped).

For example, let say that an automation rule is configured to be triggered whenever a new issue is created. When checking the audit logs of this automation rule, we can see that there is no entry in the audit logs for the issue that were skipped/missed by the automation:

Audit log entries


  • Jira is running on a cluster of at least 2 nodes

  • The issues that are skipped by the automation rules were all created from the same "unhealthy" node

  • When generating thread dumps on each node, we can see that:

    • On the "healthy" nodes (nodes where issues are not skipped), all the A4J threads are available

      Node health
    • On the "unhealthy" node (node where the issues are skipped), all the A4J threads are missing

unhealthy node
  • When logging directly on the "unhealthy" node and going to the ⚙ > Manage Apps > Manage Apps page, we can see that the Automation for Jira app is disabled on that specific node, while it's enabled on the other nodes

  • The same can be checked in the support zip generated by the nodes:

    • On the "healthy" nodes, A4J is enabled

      1 2 3 4 5 6 7 8 9 10 <plugin> <key>com.codebarrel.addons.automation</key> <name>Automation for Jira</name> <version>8.0.0</version> <vendor>Atlassian</vendor> <status>ENABLED</status> <vendor-url></vendor-url> <framework-version>2</framework-version> <bundled>User installed</bundled> </plugin>
    • On the "unhealthy" node, A4J is disabled

      1 2 3 4 5 6 7 8 9 10 <plugin> <key>com.codebarrel.addons.automation</key> <name>Automation for Jira</name> <version>8.0.0</version> <vendor>Atlassian</vendor> <status>DISABLED</status> <vendor-url></vendor-url> <framework-version>2</framework-version> <bundled>User installed</bundled> </plugin>


The reason why some Jira issues are skipped by the Automation Rules is because A4J is disabled on a specific node and the skipped issues were created/updated from that node. The exact reason why A4J is disabled on that specific node is unclear. It is possible that there were race conditions during the Jira startup of the node that prevented the A4J app from being properly enabled.


The solution is to restart the unhealthy Jira node to re-initalize the add-on and re-enable it on this node.

Please note that in some cases, A4J might still fail to be properly enabled during the re-start of the node. In such case, please raise a support ticket to Atlassian Support via our support portal so that the support team can investigate the reason why the app cannot be enabled.

Updated on May 31, 2024

Still need help?

The Atlassian Community is here for you.