# Error Handling (/docs/executions/errors)

How errors surface and how to fix common ones.



When a node fails during execution, the workflow stops and the execution is marked as failed. Here's how to diagnose and fix issues.

Where errors appear [#where-errors-appear]

* **Execution history** - failed runs show a red status
* **Run detail** - the failed node is highlighted red with an error message
* **Workflow editor** - during live execution, failed nodes show a red indicator

Error types [#error-types]

| Type             | Cause                                 | Fix                                                               |
| ---------------- | ------------------------------------- | ----------------------------------------------------------------- |
| Credential error | Missing or invalid API key            | Check [Connections](/docs/credentials) page, re-enter the key     |
| API error        | External service returned an error    | Check the error message - often rate limits or invalid parameters |
| Timeout          | Node or execution exceeded time limit | Simplify the workflow or reduce data volume                       |
| Config error     | Missing required field on a node      | Open the node settings and fill in required fields                |
| SSRF blocked     | HTTP node tried to reach a private IP | Use a public URL instead                                          |
| Wallet error     | Transaction signing failed            | Check wallet balance and connection                               |

Reading error details [#reading-error-details]

In the Run Detail view, click the failed node. The error panel shows:

* **Error message** - human-readable description
* **Error hint** - suggested fix or context for the failure

Execution timeout [#execution-timeout]

All executions have a 10-minute hard limit. If your workflow approaches this limit:

* Remove unnecessary Delay nodes
* Reduce data volumes (lower `limit` parameters)
* Split into multiple smaller workflows

Stuck executions [#stuck-executions]

Executions stuck in "running" for more than 10 minutes are automatically marked as failed by a background cleanup job. If you see this, the underlying action crashed mid-flight.

Next steps [#next-steps]

* [Credentials](/docs/credentials) - managing API keys
* [Run Detail](/docs/executions/run-detail) - inspecting execution results