Workflows

A workflow is what happens when a blueprint runs -- it's a live execution of your automation, processing real data in real time.

Blueprints vs. workflows

If a blueprint is the design, a workflow is the execution. Every time a trigger fires or you click Run once, Orqio creates a new workflow from the published blueprint.

	Blueprint	Workflow
Think of it as	A recipe	A meal being prepared
Created when	You design it in the editor	A trigger fires or you click Run once
How many	One per automation	Many -- one for each execution
Contains	Node definitions and connections	Real data, statuses, and results

What happens during a workflow

When a workflow starts:

1. The trigger receives input data (from an API call, attribute change, or test payload)
2. Nodes execute in order, following the connections you defined in the blueprint
3. Each node processes its input, performs its action, and produces output
4. The output becomes available to downstream nodes through expressions
5. When all nodes finish, the workflow completes

Workflow statuses

Each workflow run has a status:

Status	Meaning
Running	The workflow is currently executing
Completed	All nodes finished successfully
Failed	A node encountered an error and the workflow stopped

Where to find workflows

Open Executions in the Orqio app to see all workflow runs for the current workspace. From here you can:

• See the list of recent executions with their status and timing
• Click on any execution to open its report
• Filter by status, blueprint, or time range

Debugging a workflow

When a workflow doesn't behave as expected:

1. Open the execution in Executions
2. Check which node failed or produced unexpected output
3. Inspect the node's input and output data
4. Fix the blueprint, then use Run once to test again

For more on reading execution results, see Reports.

Best practices

• Monitor after publishing. Check the first few workflow executions after publishing a new blueprint version.
• Use staging for testing. Run once in staging with test data before publishing to prod.
• Review failures promptly. A failed workflow usually means a configuration issue you can fix quickly.
• Name blueprints well. Since workflow executions are listed by blueprint name, clear names help you find what you're looking for.