Workflow and Procedure errors

Workflows and Procedures are validated when authored and checked again at runtime. This prevents a deleted Tool, invalid reference, or unsafe state from turning into silent behavior.

Symptom#

A draft cannot be saved, a Workflow stops without reaching the intended node, a Procedure fails during a step, or Test Chat ends with a safe generic failure instead of executing malformed authored logic.

Cause#

Common causes include missing node or step references, cycles where they are not allowed, invalid expressions, a deleted Tool, an empty required field, and runtime transition limits. workflow_failed is the public safe code when authored execution cannot continue. Detailed provider or secret material is not returned to the caller.

Verify#

Review every validation path shown by the editor. Confirm Workflow edges target existing nodes, the first matching edge is intentional, Procedure sub-steps reference existing Procedures, and Tools still exist. In Activity, note the last successful node or step and whether the failure occurred during draft validation or execution.

Recovery#

Repair all reported paths, restore missing resources, and run the draft in a new Test Chat. For an expression, test exact input types rather than relying on coercion. For a transition-limit failure, simplify or terminate the loop. Publish only after the corrected path completes.

Escalation#

Escalate a minimal reproducible Workflow or Procedure structure with safe identifiers, the failing node or step, UTC time, and code. Remove customer text and Secret values. See Workflow runtime troubleshooting, Procedure runtime troubleshooting, and Tool safety errors.

Error code index#

• workflow_failed — authored Workflow or Procedure execution could not continue safely.

Operade does not promise that a broken draft will be made executable automatically; explicit correction and retesting are required.