Gestionnaire d'Erreurs

Catches and handles execution errors from upstream blocks. Allows defining a recovery strategy (ignore, retry, alternative branch).

Common parameters

Parameter	Type	Required	Variable	Description
strategy	choice (catch, retry, fallback)	Yes	No	Error handling strategy. (Default: "catch")
errorVariable	text	Yes	No	Variable name where the captured error will be stored, accessible via \{\{errorVariable\}\}. (Default: "error")
logError	boolean	No	No	Log errors to the system logs. (Default: true)

Parameters by strategy

catch — Catch

Catches the error and continues workflow execution.

retry — Retry

Automatically retries the failed block with configurable attempt count and delay.

Parameter	Type	Required	Variable	Description
maxRetries	number	No	No	Maximum number of retry attempts before marking the block as failed. (Default: 3, min 1, max 10)
retryDelayMs	number	No	No	Delay between each retry attempt in milliseconds. (Default: 1000, min 100, max 10000)

fallback — Fallback

Uses a fallback value if the preceding block fails.

Parameter	Type	Required	Variable	Description
fallbackValue	dynamic value	No	Yes	Value to use on error. Can be a literal, variable, or expression.

Parameters marked Variable = Yes accept the {{blockName.field}} syntax.

Output

Output variable : errorData

{
  "error": "...",
  "handled": false
}

Example

Catch an error and continue the workflow.

Input :

{}

Output :

{"error": "Connection timeout after 30000ms", "handled": true}

Tip

{{errorData.error}} contains the error message. {{errorData.handled}} confirms the error was caught. Place this block after risky blocks.