Error Handling
Every node in Blokkio has three independent error handling options, configured in the Error Handling tab of the Property Sheet.
Options at a glance
| Option | Effect |
|---|---|
| Continue on error | Workflow continues to the next node even if this node fails |
| Enable error output port | Adds a dedicated port to route failures to a separate branch |
| Retry on error | Retries the node up to N times before marking it as failed |
These options can be combined. For example, you can retry a node several times and then route persistent failures to an error branch.
Default behaviour
By default, if a node fails:
- The workflow stops at that node
- The execution is marked as Failed
- All downstream nodes are skipped
Choosing the right strategy
| Scenario | Recommended option |
|---|---|
| Transient failures (e.g. API rate limit, network blip) | Retry on error |
| Expected failures with dedicated handling logic | Error output port |
| Non-critical steps where failure is acceptable | Continue on error |
| Critical path — fail loudly | Default (no options enabled) |
Per-node scope
Error handling is configured per node, not per workflow. Each node can have a completely different strategy. This gives you fine-grained control over which steps must succeed and which can recover gracefully.