Determining if there is a missing sub-workflow or invalid transition
Stalled workflow (pre-Calgary releases)
Sometimes workflows stall or hang. This article describes some of the causes of a stalled workflow in pre-Calgary releases and how to resolve the issue.
Symptoms may include the following:
- Cannot publish workflow
- Publishing workflow takes too long
- Cannot modify checked out workflow
- Cannot start workflow
- Workflow does not start
- Workflow does not trigger
- Stalled workflow
- Missing sub-workflow
- Dangling transition
In pre-Calgary releases, a workflow can be deleted, even if it is a sub-workflow. In this case, the main flow stops running and is in a state of Finished. If you examine the context, the Workflow activity is in a state of Error and the Fault description is Subflow not found. This can also be observed in the graphical context view where the activity header is red.
Note that a fault of Workflow not found can also occur if the subflow is checked out by another user and there is no published version.
Sometimes a transition can be pointing to a non-existent activity. In this case, the graphical workflow editor does not draw any transition line and it is difficult to detect a dangling transition.
The symptom is that the workflow context simply stops running and is stuck in a state of executing.
To fix this situation, you must examine the Workflow Transition History related list in one of the contexts for the workflow. The To column is blank for a dangling transition. After you find this transition, navigate to the Workflow Version and click on the Activity that originates the transition. The Activity form has a related list of transitions from this activity. Find and delete the offending transition.