Jobs have completed but workflow duration timer continues to run

Overview

We have sometimes seen a workflow timer continue to run even after all jobs have completed. This can be concerning for many reasons. However, this is often times simply an inconsistency in the workflow state. 

 

Resolution

You can use the CircleCI v2 API to confirm that none of the workflows jobs are currently running by using the Get a workflow's jobs endpoint. In a small amount of cases, the status of a job may remain in "running" even though all steps have completed. 

 

You can confirm a workflow has completed by using the Get a workflow endpoint. If the following present in the response of the API call, the workflow is not currently running and has run to completion. This stands true even if a workflow's jobs remain "running". 

"stopped_at" : "null"

 

You may also use the CircleCI v2 API to Cancel a job or Cancel a workflow. Please note that you may only cancel a build that was triggered up to 3 months ago. 

 

Lastly, you can leverage the insight dashboard to check credit usage. Please keep in mind that the compute minutes for the workflow may appear to be above average but the credit usage should be approximately the same as other builds. 

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Article is closed for comments.