> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/harness-platform/use-harness-platform/pipelines/failure-handling/timeout-settings.md).

# Timeout settings

Timeout settings help prevent steps, stages, and pipelines from running excessively long. For example, this can help end a pipeline naturally if a step enters an endless loop or other long-lasting or infinite failure condition.

### Step timeouts <a href="#step-timeouts" id="step-timeouts"></a>

When configuring a step, you can set the step **Timeout** under the **Step Parameters** tab. The default is usually 10 minutes.

![Step Timeout](/files/AjH8feIkQZyEWucd4bkP)

Step timeouts mark steps as expired in the following scenarios:

* The step does not complete before the configured timeout.
* The stage or pipeline reaches the stage/pipeline timeout limit when the step is still running.

### Stage timeout <a href="#stage-timeout" id="stage-timeout"></a>

Find the stage **Timeout** settings under **Overview** > **Advanced** when configuring your stage.

<figure><img src="/files/bofhMw62EB7MEc1EovBt" alt=""><figcaption><p>Click to view full size image</p></figcaption></figure>

Stage timeouts mark stages as expired in the following scenarios:

* The stage does not complete before the configured timeout.
* The pipeline reaches its timeout limit when the stage is still running.

{% hint style="info" %}
**NOTE**

When a stage time out is less than it's total step execution time, the failure strategy applied is `EXPIRE_ALL`, preventing rollback. This occurs because child nodes (steps) inherit the expired status from the stage, stopping further execution.
{% endhint %}

### Pipeline timeouts <a href="#pipeline-timeouts" id="pipeline-timeouts"></a>

Find the **Pipeline Timeout Settings** under the **Advanced Options** section in the right navbar.

<figure><img src="/files/gSPzeNywUR8beRSw3u4W" alt=""><figcaption><p>Click to view full size image</p></figcaption></figure>

The pipeline timeout applies to the duration of the entire pipeline. It does not override stage/step timeouts, but stages and steps will timeout if the pipeline timeout limit is hit while a stage/step is running.

{% hint style="warning" %}
**APPROVALS**

Approval steps and stages can *pause* execution but they *do not* stop the pipeline timeout counter. Make sure that the pipeline timeout setting accommodates the time required for approvals.
{% endhint %}
