ToolErrorCode

Why an invocation failed, a snake_case code beside its status (1.49.0): an EgressDenialReason for blocked, phi_in_query_string, http_status, response_not_json, response_invalid, response_too_large, connect_failed, resolution_failed, tls_failed, deadline_exceeded, no_handler, handler_error (a tool.result with ok false), already_resolved and signing_secret_missing (an http Tool in a Session configuration without the signing secrets); from 1.50.0 also invalid_arguments (the status of the same name: the arguments failed the parameters), refused_by_policy (the status of the same name: a terminal action at on_tool_call), interrupted (the caller interrupted or the Call ended while the Tool ran, and its result was discarded) and capability_not_available (the Tool needs something the worker does not build, such as an mcp Tool). From 1.60.0 also the codes of a bound tool and of a refused Run (KNOWN_TOOL_ERROR_CODES): connection_not_active, auth_expired, scope_missing, vendor_unavailable, vendor_schema_mismatch, schema_drift (a pinned MCP tool whose contract changed), tool_unavailable, tool_error (an MCP result with isError), protocol_error, input_required_unsupported, result_invalid, rate_limited, integration_unavailable (the integrations service could not be reached), phi_detected, recipient_opted_out, spend_cap_reached and run_quota_reached. KnownToolErrorCode lists the codes this version knows besides the egress reasons. Never free text or content. Codes are added in later minor versions.

A value of type string.