Error Handler
Category: Control
Node id: error-handler
Provides error handling, recovery, and fallback logic for pipelines with catch, fallback, transform, log, and retry strategies
What it does
- Five error strategies: catch, fallback, transform, log_and_continue, retry_info
- FHIR OperationOutcome error format support
- Error suppression with pipeline continuation
- Fallback values from config or upstream input
- Retry metadata with attempt tracking and backoff info
Use cases
- Catch and suppress non-critical errors in data pipelines
- Provide fallback values when external FHIR servers are unavailable
- Transform errors into FHIR OperationOutcome resources
- Log errors and continue processing remaining records
Runtime
- Performance tier:
fast
Input ports
| Name | Type | Required | Description |
|---|---|---|---|
error | text | No | Error message string |
error_data | json | No | Structured error data |
input_data | json | No | Original input data to pass through |
fallback | any | No | Fallback value (for fallback strategy) |
Output ports
| Name | Type | Required | Description |
|---|---|---|---|
result | json | No | Full error handling result with strategy details, error info, and recovery metadata |
recovered | boolean | No | Whether the error was recovered from (caught, fallback used, or logged) |
success | boolean | No | Whether error handling completed |
Settings
Basic
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Strategy | strategy | enum | Yes | catch | catch, fallback, transform, log_and_continue, retry_info | Error handling strategy |
| Severity | severity | enum | No | error | error, warning, info | Error severity level (for catch strategy) |
| Suppress Error | suppress_error | boolean | No | false | Suppress the error and continue pipeline execution | |
| Default Value | default_value | json | No | Default output value when error is caught | ||
| Fallback Value | fallback_value | json | No | Fallback value to use (for fallback strategy) |
Advanced
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Output Format | output_format | enum | No | standard | standard, fhir_operation_outcome, json | Error output format (for transform strategy) |
| Error Code | error_code | string | No | PIPELINE_ERROR | Custom error code (for transform strategy) | |
| Max Retries | max_retries | number | No | 3 | min 0; max 100 | Maximum number of retries (for retry_info strategy) |
| Retry Delay (seconds) | retry_delay_seconds | number | No | 5 | min 0; max 3600 | Delay between retries in seconds |
Errors
| Code | Description |
|---|---|
UNSUPPORTED_STRATEGY | The specified error handling strategy is not recognized |
MISSING_FALLBACK | Fallback strategy requires fallback_value config or fallback input |
Runtime notes
- Output shape under 'result' varies by strategy: catch has caught/error/suppressed, fallback has output/used_fallback, transform has error object, retry_info has can_retry/retry_count/next_retry
- Use 'recovered' boolean to branch the pipeline — true means the error was handled and execution can continue
- Transform strategy with output_format='fhir_operation_outcome' produces a valid FHIR OperationOutcome resource
- retry_info reads retry_count from error_data to track attempts — wire error_data from a retry loop to maintain state
See Build any workflow for how to put nodes together and Ports, types and data flow for how port types connect.
Something unclear? Send documentation feedback by email.