Missing Workflow and Issue
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
Problem
This issue happens normally due to data corruption which is caused by connection issue to the database
The following appears in the atlassian-jira.log
1
2
3
4
5
2016-08-22 10:20:40,601 http-bio-8080-exec-10 ERROR xxx 680x628793x1 lptcgy xxx /secure/admin/workflows/ViewWorkflowSteps.jspa [web.util.component.RequestComponentManager] java.lang.IllegalStateException: No live workflow was found for 'xxx'.
java.lang.IllegalStateException: No live workflow was found for 'xxx'.
2016-08-22 10:52:11,311 http-bio-8080-exec-11 ERROR xxx 712x636959x2 d6cqok xxx /secure/admin/workflows/ListWorkflows.jspa [webwork.util.ValueStack] query="activeWorkflows/empty" {[id="activeWorkflows" type="8" values=""]} {[id="empty" type="8" values=""]}
java.lang.reflect.InvocationTargetExceptionDiagnosis
To verify if you are being affected by this problem, please perform the following SQL query in JIRA's database accordingly:
PostgreSQL and Oracle
1
SELECT id, workflow FROM workflowschemeentity WHERE workflow NOT IN (SELECT workflowname FROM jiraworkflows);MS-SQL database
1
SELECT id, workflow FROM workflowschemeentity WHERE workflow collate SQL_Latin1_General_CP437_CS_AS NOT IN (SELECT workflowname FROM jiraworkflows);MySQL database
1
SELECT id, workflow FROM workflowschemeentity WHERE BINARY workflow NOT IN (SELECT workflowname FROM jiraworkflows);Cause
This issue can happen if one or more workflow names stored in the workflowschemeentity table do not match any workflow names stored in the jiraworkflows table. One reason for this could be a Workflow Scheme that is associated with a deleted Workflow in the database, or there is an inconsistency in the characters' cases of the workflow name (e.g. "JIRA workflow" vs "JIRA Workflow").
The 'jira' workflow is a Read-only System Workflow so it is not in the 'jiraworkflows' table. If running the Diagnosis queries returns that workflow, then it is normal.
Solution
Resolution
Always back up your data before making any database modifications. If possible, test any alter, insert, update, or delete SQL commands on a staging server first.
Try to add the missing workflow from the logs again in JIRA. And retest. If does not work, proceed with below.
Shutdown JIRA.
After identifying the inconsistent workflow in the
workflowschemeentitytable, please update the entry/entries with the valid workflow name by running the following SQL update statement:1UPDATE workflowschemeentity SET workflow = '<Correct Workflow Name>' where id=<ID of incorrectly named workflow>;ℹ️ Remember to change the
Workflow Nameand ID to the correct value accordingly.(Oracle Only): Commit the transaction with the following:
1COMMIT;After updating the related record(s) in the database, restart JIRA for the changes to take effect.
Was this helpful?