# Why is a completed workflow still in the running state?

**URL:** <https://community.orkes.io/t/why-is-a-completed-workflow-still-in-the-running-state/119>\
**Category:** FAQ\
**Created:** [January 22, 2025, 12:55am UTC](https://community.orkes.io/t/why-is-a-completed-workflow-still-in-the-running-state/119 "2025-01-22T00:55:39Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![orkes\_community](https://sea2.discourse-cdn.com/flex002/user_avatar/community.orkes.io/orkes_community/32/24_2.png) [@orkes\_community](https://community.orkes.io/u/orkes_community)\
**Post date:** [January 22, 2025, 12:55am UTC](https://community.orkes.io/t/why-is-a-completed-workflow-still-in-the-running-state/119/1 "2025-01-22T00:55:40Z")

</div>

Occasionally, all steps in a workflow complete, but it remains in the running state. This may be due to indexing issues or misconfigurations. Ensure indexes are correctly synchronized and check if the decider queue is removing the workflow prematurely.