# Workflow still running after WorkflowTaskTimedOut

**URL:** <https://community.temporal.io/t/workflow-still-running-after-workflowtasktimedout/10951>\
**Category:** Community Support\
**Created:** [February 8, 2024, 10:21pm UTC](https://community.temporal.io/t/workflow-still-running-after-workflowtasktimedout/10951 "2024-02-08T22:21:35Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![myusername](https://avatars.discourse-cdn.com/v4/letter/m/c77e96/32.png) [@myusername](https://community.temporal.io/u/myusername)\
**Post date:** [February 8, 2024, 10:21pm UTC](https://community.temporal.io/t/workflow-still-running-after-workflowtasktimedout/10951/1 "2024-02-08T22:21:35Z")

</div>

I’m using the Ruby SDK. I’m seeing that whenever my workflow times out (the timeout is StartToClose), the workflow is still shown as running in the UI. This can’t be expected, right? How do I get the workflow to properly have that “Timed out” status?

 ![Screenshot 2024-02-08 at 14.18.35](https://us1.discourse-cdn.com/flex016/uploads/temporal/original/2X/b/baa9b22cde3aec8506b064ed473502e7429e054c.png)

---

<div class="post-metadata">

**Author:** ![tihomir](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/tihomir/32/6580_2.png) [@tihomir](https://community.temporal.io/u/tihomir)\
**Post date:** [February 8, 2024, 10:31pm UTC](https://community.temporal.io/t/workflow-still-running-after-workflowtasktimedout/10951/2 "2024-02-08T22:31:30Z")

</div>

> my workflow times out (the timeout is StartToClose),

The workflow execution itself did not time out, but the workflow task which has a 10s StartToClose timeout (time from when a workflow task is dispatched to your worker until your worker respond back with workflow task completion).  
The workflow task is being retried, possible on different worker and execution seems “stuck”, but yes its still running allowing you to fix issue and for it to continue.

This can be indication of number of things like high cpu on worker, possible infinite loops in workflow code/data converter, calling downstream apis in workflow code or blocking workflow code on non-Temporal apis are the biggest culprits.

---

<div class="post-metadata">

**Author:** ![myusername](https://avatars.discourse-cdn.com/v4/letter/m/c77e96/32.png) [@myusername](https://community.temporal.io/u/myusername)\
**Post date:** [February 8, 2024, 10:50pm UTC](https://community.temporal.io/t/workflow-still-running-after-workflowtasktimedout/10951/3 "2024-02-08T22:50:02Z")

</div>

Thanks, that’s super helpful! Is there a way to limit the number of times the workflow task is retried?

---

<div class="post-metadata">

**Author:** ![maxim](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/maxim/32/8_2.png) [@maxim](https://community.temporal.io/u/maxim)\
**Post date:** [February 9, 2024, 6:43pm UTC](https://community.temporal.io/t/workflow-still-running-after-workflowtasktimedout/10951/4 "2024-02-09T18:43:35Z")

</div>

You can set the workflow run or execution timeout to limit the duration of such retries.