Retries
:::note Plan requirement Retry on error is available on Pro and Enterprise plans. :::
Retries automatically re-execute a failed node a configured number of times before giving up. This is useful for transient failures such as network timeouts or API rate limits.
Enabling retries
- Click the node to open its Property Sheet.
- Go to the Error Handling tab.
- Toggle Retry on error before failure.
Two additional fields appear:
| Field | Description |
|---|---|
| Attempts | Maximum number of retry attempts (not counting the original attempt) |
| Delay between attempts | Milliseconds to wait between each retry |
Behaviour
- The node executes.
- If it fails, Blokkio waits for the configured delay, then retries.
- Steps 1–2 repeat until the node succeeds or the attempt limit is reached.
- If all attempts fail:
- If an error port is configured, execution routes through it.
- Otherwise, the workflow stops and the execution is marked as Failed.
Example
For an external API call that occasionally rate-limits (HTTP 429):
- Attempts:
3 - Delay:
5000(5 seconds between retries)
The node will try up to 4 times in total (1 original + 3 retries) with a 5-second pause between each.
Delay guidance
| Use case | Suggested delay |
|---|---|
| Network blip | 1000–2000 ms |
| API rate limit (per-second) | 2000–5000 ms |
| API rate limit (per-minute) | 60000 ms |
| Upstream service restart | 10000–30000 ms |