Error codes

Error code suggestions

For authentication, password-update, and incorrect-input failures, the Maintenance Agent can compare its diagnosis with your approved workspace error codes. When no code matches and Error Code Generation is enabled, it creates a pending suggestion for review instead of silently approving a new code. After approval under Error Handling > Error Codes, future matching failures can return the code in run results and execution.failed webhooks. Approved error codes can also define actions such as fail and notify, retry, or stop the run and pause its workflow or vault credential. When Decision Required asks a person about a failure, the card can also suggest an error code for it. See Add Error Code.

Error code actions

The action on an error code decides what happens to a run that fails with it.

Action	What happens
`alert`	The run fails and you are notified. This is the default
`retry`	The run is requeued up to Retries times (once if unset), waiting Retry after seconds (at least 10; the default backoff if unset). It follows your workflow’s `allow_requeue`, dry-run marker and `max_retries` settings, so a run that already did work is not replayed
`pause_workflow`	The run ends as `execution.stopped` and its workflow is paused. See Pausing
`pause_credential`	The run ends as `execution.stopped` and the vault credential it used is paused. See Pausing

An action applies to codes matched in the error message and to codes the Maintenance Agent matches from your workspace codes. Codes added from a Decision Required card start as alert unless you pick another behavior.

Getting Started

Concepts

API Reference

SDK

Integrations

Error code suggestions

Error code actions