NodeErrorHandlerConfig class. You can attach this configuration to both tool nodes and agent nodes.
NodeErrorHandlerConfig defines how a node behaves when an execution error occurs. It controls retry behavior, error messaging, and redirection within the agentic workflow flow.
When you attach this configuration to a node, you allow the flow engine to evaluate errors at runtime and decide how execution continues.
To configure error handling, create a NodeErrorHandlerConfig instance and pass it to a node when you call tool() or agent() in your agentic workflow.
Python
Describes the error that occurred.The flow engine logs this message for observability and debugging.The agentic workflow flow does not display this message to the user unless you explicitly expose it through a user flow or UI element.
Specifies how many retry attempts occur after a failure.If you set this value to
0, the node follows the configured error behavior immediately.If you omit this value, the platform default retry behavior applies.Defines the delay between retries in milliseconds.This setting applies only when
max_retries is greater than 0.Defines how the agentic workflow flow responds when the node fails.Supported values:
-
show_message: Stops the agentic workflow after displaying an error message to the user. Use this option when no alternate path applies. -
branch: Redirects the agentic workflow flow to an alternate path using the edge specified byerror_edge_id. Use this option to handle expected failures, guide users to a recovery path, or invoke fallback logic when tools or external services return errors. This option suits agentic workflows that rely on services with variable availability.
Specifies the edge that execution follows when
on_error="branch" is set.This value must match an edge defined with aflow.edge(...).If no matching edge exists, the agentic workflow fails during validation or execution.Python [Expandable]

