Troubleshooting Jira automation: SOME ERRORS and FAILURE status
Platform Notice: Data Center - This article applies to Atlassian products on the Data Center platform.
Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles 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 can fail for various reasons. Two of the most common statuses the audit logs might show are:
- Some error status: SOME ERRORS
- Failure status: FAILURE
Understanding the meaning of the errors reported in the audit logs and how to fix them can be a challenge. The purpose of this article is to list the most common errors and the KB articles (or bug tickets) which are related them, which will help fix them.
On this page:
Environment requirements
Starting from Jira Data Center 10.0, we integrated Jira automation (formerly Automation for Jira) as part of Jira Data Center (both Software and Service Management), offering you the convenience of upgrading either through Jira or the Universal Plugin Manager (UPM). To streamline and enhance your experience with Jira automation, we've made the decision to solely offer it as a bundled version starting from Jira 10.0.
This guide assumes that you're using:
- Jira Data Center 8.0.0 or later
- Jira automation Data Center 7.4.0 or later
Error scenarios
A rule failed to complete with the SOME ERRORS status
If a rule failed with the SOME ERRORS status, look for the error that was shown in the audit logs in the list below and open the corresponding article or bug report to resolve it:
- No transitions to specified status could be found for issues
- Can't assign to unknown user
- The selected resolution cannot be chosen during this action
- Service proxy has been destroyed
- No fields or field values to edit for issues
- Field XXXX does not exist or you do not have permission to view it
- Unknown fields set during edit, they may be unavailable for the project/type
- No issue type selected. (issuetype), No project selected. (pid)
- Provided URL is not present in Jira allowlist or request from anonymous users is not enabled
- You must have a licensed service project to run JQL queries on SLAs
- Could not find create meta data for project/typeId" message in "Create Issue
- The label 'XXXXXX' contains spaces which is invalid (labels)
- Internal server error (with the 500 error while sending a webhook to Confluence)
- No serializer found for class com.atlassian.jira.issue.history.ChangeItemBean and no properties discovered to create BeanSerializer
- SSLPeerUnverifiedException: Certificate for <subdomain.webhook.office.com> doesn't match any of the subject alternative names
- class com.onresolve.scriptrunner.automation.ExecuteScriptIssueActionV2 cannot be cast to class com.codebarrel.automation.api.thirdparty.AutomationRuleComponent
- Could not find valid 'id' or 'name' in resolution object. (resolution)
- Failed to get value for now
- Unknown fields set during transition. Field may not be on transition screen. Fields ignored
- you do not have the permission to associate a worklog to this issue
- Error marking step #XXXXX finished: root cause: Tried to update an entity that does not exist
- User '<SOME_USERNAME>' is not valid for this user picker. (customfield_XXXXX)
A rule failed to complete with the FAILURE status
If a rule failed with the FAILURE status, look for the error that was shown in the audit logs (if there was any) in the list below and open the corresponding article or bug report to resolve it:
- Failure in rules without any error, caused by third-party actions
- Either you or the rule actor for this rule is missing some required permissions
- Cannot invoke "javax.servlet.http.HttpServletRequest.getParameterMap()" because the return value of "com.atlassian.jira.web.ExecutingHttpRequest.get()" is null
- java.lang.NoClassDefFoundError: com/codebarrel/automation/api/thirdparty/AutomationRuleComponent
- java.lang.StringIndexOutOfBoundsException: begin X, end Y, length Z