WorkflowNodeFailureCode
Why a Workflow node took on_failure (1.59.0; workflows-and-processes.md sections 5.1, 5.2 and 6): gather no_match, timeout or max_attempts; tool error, timeout, blocked, no_handler or invalid_arguments; transfer busy, no_answer or refused; retrieve timeout, provider_error or no_grant; evaluate and condition invalid_input, engine_error or unknown_outlet; rule_table no_rule_hit, schema_invalid or engine_error; transform type_error; and the agentic nodes of a later release schema_invalid, timeout, provider_error, blocked or turn_cap; from 1.60.0 tool and retrieve also binding_unavailable, a Tool or Knowledge binding the node names and the Session lacks, dropped at claim; from 1.62.0 (roadmap slice 2.16) start_call call_failed (its Call ended on a reason of the on_failure outlet) or max_wait_elapsed (admission kept refusing on concurrency until max_wait), and emit_event refused. A reader treats an unknown code as a failure it does not interpret.
An enumeration of 22 values.
Values
no_matchtimeoutmax_attemptserrorblockedno_handlerinvalid_argumentsbusyno_answerrefusedprovider_errorno_grantinvalid_inputengine_errorunknown_outletno_rule_hitschema_invalidtype_errorturn_capbinding_unavailablecall_failedmax_wait_elapsed