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 during execution.
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.
Account setting enabled: You must enable Allow users to mark a running Step as failure in your Harness account's default settings.
Mark a pipeline as failed
Perform the following steps to mark a running pipeline as failed:
Navigate to the pipeline execution details page.
Click Mark as Failed.
After you mark a pipeline as failed, Harness fails running and queued stages. Completed stages are not marked as failed.
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: Configure automated failure handling strategies for pipeline stages and steps.
Abort pipeline, stage, or step: Abort running executions instead of marking them as failed.
Last updated
Was this helpful?