Build
Read executions in Duaer
In Duaer, one execution is one run of a workflow. The Executions list shows success, error, canceled, running, queued, and waiting.
What one execution is
One execution is one run from the trigger until it finishes, fails, is canceled, or stops on Wait. Hosted plans count these runs. Refer to Duaer plans and credits. A manual test on the canvas is also an execution. Its mode is manual.
Open the list
- In the left sidebar, select Executions.
- Filter by status, or pick one workflow first. Statuses include Succeeded, Error, Canceled, Running, Queued, and Waiting.
- Select a row to open that execution. The canvas is read-only. Change nodes from the workflow tab.
Mode says how it started: manual, trigger, webhook, error, retry, or integrated. Waiting means the run reached Wait and has not resumed yet. A canceled execution stays canceled. Refer to canceled executions.
Retry a failure
On a failed execution, select Retry execution. Both options continue from the node that failed:
- Retry with the currently saved workflow uses the nodes on the canvas now.
- Retry with the original workflow uses the nodes from that execution.
Questions
Does a manual test in Duaer count as an execution?
Yes. It shows in Executions with mode manual. Hosted plans bill executions, not seats.
In this section
View the Duaer data pool
In Duaer, the data pool lists deliverables from successful production runs of digital employees. The sidebar item sits under Digital employees. Manual test runs do not write here.
ManageDebug a past execution in Duaer
In Duaer, open a past execution and use Debug in editor to pin that run’s data on the canvas, then change a node and run again.
ManageSave and publish a workflow in Duaer
In Duaer, edits stay a draft until you publish. Schedules, webhooks, and production runs use the published version.