> 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/docs/es/acciones/workflow-concepts/run-once/error-handling.md).
# Manejo de errores
Continúa el flujo de trabajo usando lógica ramificada si el paso devuelve un error
## ¿Qué es el manejo de errores?
El manejo de errores te permite decidir qué sucede cuando un paso falla en tu flujo de trabajo. Puedes terminar todo el flujo de trabajo cuando ocurre un error o permitir que siga ejecutándose a pesar del error.
Si la salida de un paso es esencial para los pasos posteriores, elige terminar el flujo de trabajo cuando ese paso falle. Si el flujo de trabajo puede continuar sin la salida de un paso en particular, puedes configurarlo para que continúe a pesar de los errores.
## Cómo manejar los pasos fallidos
1. Selecciona `Continuar` en lugar de `Terminar flujo de trabajo` si el paso falla
2. Añade una condición donde la condición compruebe si el `error` del paso existe, por ejemplo: `step_1.error`
3. Añade pasos o acciones alternativas para ejecutar cuando ocurra un error
{% @arcade/embed url="" 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/docs/es/acciones/workflow-concepts/run-once/error-handling.md?ask=&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.
