| - |
'''There are problems that can occur/present themselves which cause workflows to be stuck in various statuses on the AnthillPro server. Sometimes the only way to resolve this issue is through database manipulation. Some examples of SQL statements that work are listed below with explanations.'''
|
+ |
While AnthillPro is a great product for build & deploy automations, there are problems that can occur/present themselves which cause workflows to be stuck in various statuses on the AnthillPro server. Not only is this seen with workflow cases, but it may happen with job traces, and command traces as well. These errors can occur if a persistant did not update within the database correctly, or if the step threw an error in a manner that caused processing to cease, and an "update" event could not be fired. Usually, the only way to resolve this issue is through database manipulation. Some examples of SQL statements that work are listed below with explanations.
|
| - |
==== Set all running workflows to "aborted" status ====
|
+ |
Workflow cases may not update properly if the WorkflowEndEvent does not fire. In that case, the SQL below will update the WorkflowCase.
|
| - |
<pre> UPDATE WORKFLOW_CASE SET STATUS = 'Aborted' WHERE STATUS = 'Running';</pre>
|
+ |
== SQL to Set All Running Workflows to a Status ==
|
| |
|
+ |
<pre> UPDATE WORKFLOW_CASE SET STATUS = 'XX' WHERE STATUS = 'YY';</pre>
|
| |
==== Set a specific build life id to "aborted" status ==== |
|
==== Set a specific build life id to "aborted" status ==== |
