Troubleshooting Workflows with an Undefined End Time


You may be experiencing the following with a workflow where a job has been completed or cancelled, but:

  • You experience an error in a job that says:

"This job appears to have stopped responding, try re-running it."

  • The workflow is completed or cancelled, but a job still has a timer running incrementally indefinitely
  • The workflow is completed or cancelled, but the UI instead shows an "*" or a "?" with:

"Actual time could not be calculated."


This inconsistency is due to the UI being dependent on data that is not guaranteed to be populated in our database that the UI uses.

We recognize that the accuracy of time reporting is important in the UI and are currently working to make our systems more robust and efficient in order to address this UI inconsistency

Please also be aware that credit consumption calculations are not affected. They are based on an individual job reporting usage that is separate from our UI system. For further analysis on job workflow credit consumption, you can also utilize our API V2 Endpoint:{org}/{project}/workflows/{workflow-name}?branch={branch-name}

You can reference the Workflow ID to search among your API results. For example:

    "id" : "9c0cc99-i99x-9999-99c0-9c9c0i299000",
    "duration" : 999,
    "status" : "success",
    "created_at" : "2022-12-03T00:50:06.216Z",
    "stopped_at" : "2022-12-03T00:57:17.796Z",
    "credits_used" : 72,
    "branch" : "master",
    "is_approval" : false


Additional Resources

If you have any additional questions, feedback, or interest in accurate end time in the UI or API, please feel free to reach out for additional assistance at CircleCI Support.

Was this article helpful?
1 out of 2 found this helpful



Article is closed for comments.