Saltar al contenido principal

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​

NameTypeRequiredDescription
errortextNoError message string
error_datajsonNoStructured error data
input_datajsonNoOriginal input data to pass through
fallbackanyNoFallback value (for fallback strategy)

Output ports​

NameTypeRequiredDescription
resultjsonNoFull error handling result with strategy details, error info, and recovery metadata
recoveredbooleanNoWhether the error was recovered from (caught, fallback used, or logged)
successbooleanNoWhether error handling completed

Settings​

Basic​

SettingNameTypeRequiredDefaultAllowed valuesDescription
StrategystrategyenumYescatchcatch, fallback, transform, log_and_continue, retry_infoError handling strategy
SeverityseverityenumNoerrorerror, warning, infoError severity level (for catch strategy)
Suppress Errorsuppress_errorbooleanNofalseSuppress the error and continue pipeline execution
Default Valuedefault_valuejsonNoDefault output value when error is caught
Fallback Valuefallback_valuejsonNoFallback value to use (for fallback strategy)

Advanced​

SettingNameTypeRequiredDefaultAllowed valuesDescription
Output Formatoutput_formatenumNostandardstandard, fhir_operation_outcome, jsonError output format (for transform strategy)
Error Codeerror_codestringNoPIPELINE_ERRORCustom error code (for transform strategy)
Max Retriesmax_retriesnumberNo3min 0; max 100Maximum number of retries (for retry_info strategy)
Retry Delay (seconds)retry_delay_secondsnumberNo5min 0; max 3600Delay between retries in seconds

Errors​

CodeDescription
UNSUPPORTED_STRATEGYThe specified error handling strategy is not recognized
MISSING_FALLBACKFallback 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.

¿Algo no está claro? Envíe sus comentarios sobre la documentación por correo electrónico..