> 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-ai/use-harness-platform/pipelines/failure-handling/mark-as-failed-pipeline.md).

# Mark pipeline as failed

Mark a pipeline as failed during execution to stop all running and queued stages.

You can manually stop a running pipeline by marking it as failed. The **Mark as Failed** button on the pipeline execution details page allows you trigger failure handling for the pipeline and its currently running stages.

***

### What you will learn from this topic

* How to [mark a pipeline as failed](#mark-a-pipeline-as-failed) during execution.
* How to understand the [difference between marking a stage as failed and marking a pipeline as failed](#marking-a-pipeline-vs-a-stage-as-failed).

***

### Before you begin

* **Pipeline permissions:** You must have Execute permissions on pipelines to mark a pipeline as failed. For more information, refer to [Manage roles](/harness-ai/use-harness-platform/platform-access-control/add-manage-roles.md).
* **Account setting enabled:** You must enable **Allow users to mark a running Step as failure** in your Harness account's [default settings](/harness-ai/use-harness-platform/settings/default-settings.md).

***

### Mark a pipeline as failed

Perform the following steps to mark a running pipeline as failed:

1. Navigate to the pipeline execution details page.
2. Click **Mark as Failed**.

![](https://173309742-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3F2TpHXhur2QtQnORSM9%2Fuploads%2Fgit-blob-21a33aa5d1c72d20997c5da9995d0252084cd539%2Fmake-pipeline-as-failed1.png?alt=media)

After you mark a pipeline as failed, Harness fails `running` and `queued` stages. Completed stages are not marked as failed.

{% hint style="info" %}
If a pipeline is configured with failure strategy like `Ignore Failure` or `Retry`, the execution might continue even after `Mark as Failure` is sent.
{% endhint %}

***

### Marking a Pipeline vs. a Stage as Failed

You can manually mark either an entire pipeline or an individual stage as failed. The behavior differs depending on whether other stages are running at the same time.

* If only one stage is running when you mark the stage or pipeline as failed, both options have the same effect.
* If multiple stages are running in parallel, marking the **pipeline** as failed stops all running stages. Marking a **stage** as failed stops only that stage.

***

### Next steps

* [Define a failure strategy on stages and steps](/harness-ai/use-harness-platform/pipelines/failure-handling/define-a-failure-strategy-on-stages-and-steps.md): Configure automated failure handling strategies for pipeline stages and steps.
* [Abort pipeline, stage, or step](/harness-ai/use-harness-platform/pipelines/failure-handling/abort-pipeline.md): Abort running executions instead of marking them as failed.

{% @harness-feedback/feedback module="harness-ai" pagePath="harness-ai/use-harness-platform/pipelines/failure-handling/mark-as-failed-pipeline" %}