Executions and monitoring

Monitor and manage workflow executions to track progress, debug issues, and provide input to paused workflows.

Manual execution

Start a workflow manually from the editor by clicking Execute in the toolbar. You can provide input variables before starting the run. Use manual execution for testing and one-off runs during development.

Execution states

Each execution moves through a series of states as it progresses.

Status	Description
pending	Queued for execution
running	Currently executing
paused	Waiting for input at a wait_for_input node
completed	Finished successfully
failed	Encountered an error

Monitoring executions

View the execution list for each workflow, showing status, start time, and duration. The list updates in real time, so you can watch executions progress without refreshing.

Click an execution to see step-by-step details, including which nodes have completed, which are currently running, and any errors encountered.

Tip

Use the execution list to quickly identify failed runs. Filter by status to focus on executions that need attention.

Execution details

Each execution shows a detailed log of every node that ran, including:

• Inputs — the data passed into the node
• Outputs — the data produced by the node
• Timing — how long the node took to execute
• Status — whether the node succeeded or failed

This step-by-step view is invaluable for debugging workflows and understanding how data flows through each node.

Paused executions

Workflows with wait_for_input nodes pause execution until input is provided. When a workflow reaches a wait_for_input node, its status changes to paused and it waits for external input before continuing.

Provide input via:

• Dashboard — open the paused execution and enter the required input directly
• API callback — send input programmatically using the callback endpoint

Durable execution callbacks

For long-running external processes, use the callback endpoint to resume a paused workflow programmatically:

POST /api/v3/organisations/{org}/ai/chat/callback

Send the required input data in the request body. The workflow resumes from the paused node and continues executing the remaining steps.

curl -X POST https://api.quantcdn.io/api/v3/organisations/{org}/ai/chat/callback \
  -H "Authorization: Bearer {token}" \
  -H "Content-Type: application/json" \
  -d '{"executionId": "{executionId}", "input": "Approved"}'

Replace {org} with your organisation identifier, {executionId} with the paused execution’s ID, and {token} with your API token.

Note

Durable execution callbacks allow you to integrate human-in-the-loop approval steps and external system responses into your workflows.

Deleting executions

Remove old execution records from the execution history to keep your workspace tidy. Deleting an execution removes its logs and output data permanently.

To delete an execution, select it from the execution list and click Delete. You can also delete multiple executions at once by selecting them in bulk.

Next steps

• Workflow editor — design and edit your workflows
• Triggers — configure how workflows are started
• Get started — create your first workflow