> For the complete documentation index, see [llms.txt](https://docs.airops.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.airops.com/actions/workflow-concepts/run-once/error-handling.md).

# Error Handling

Continue workflow using branched logic if the step returns an error

## What is error handling?

Error handling lets you decide what happens when a step fails in your workflow. You can either terminate the entire workflow when an error occurs or allow it to continue running despite the error.

If a step's output is essential for subsequent steps, choose to terminate the workflow when that step fails. If the workflow can proceed without a particular step's output, you can configure it to continue despite errors.

<figure><img src="https://3762890407-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX2n5yPRPynbnWuO4SH0M%2Fuploads%2Fgit-blob-354d74ef2b4b7a414da4e356c548e1b2833d9e4d%2FCleanShot%202025-02-26%20at%2006.59.55%402x.png?alt=media" alt=""><figcaption></figcaption></figure>

## How to Handle Failed Steps

1. Select `Continue` instead of `Terminate Workflow` if the step fails
2. Add a conditional where the condition checks if the `error` from the step exists e.g. `step_1.error`
3. Add alternative steps or actions to execute when an error occurs

{% @arcade/embed url="<https://app.arcade.software/share/DKDlZVzy53bV2TOmBxNP>" flowId="DKDlZVzy53bV2TOmBxNP" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.airops.com/actions/workflow-concepts/run-once/error-handling.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.