Skip to main content
A workflow run is one execution attempt created from trigger data. Each run stores its input payload, status, node outputs and errors, and a snapshot of the workflow graph selected when the run was queued.

​
Open run history

WorkflowDog provides two views: Both views update active Pending and Running rows automatically. The project view shows the workflow name, date, duration, status, and run actions. The editor history lets you select a run and display its data directly on the canvas.

​
Run statuses

Completed does not mean every node succeeded. A completed run with an amber warning icon contains one or more node errors. Open the run and inspect the affected nodes.
Common run-level Failed reasons include:
  • The workflow was paused.
  • The project had no remaining run credits and no active usage billing.
  • The project’s payment state did not allow new usage.
  • The execution worker encountered an unrecoverable error.
See Troubleshoot workflow runs for a diagnostic flow.

​
Inspect a run on the canvas

Select a row from Run History in the workflow editor. Node outputs and errors become available for that run, and the editor offers two canvas modes.
Shows the saved graph snapshot associated with the run. Use this mode to answer: “What graph actually ran?”The snapshot cannot be edited. It remains stable even after you change the current workflow.
Use Newer and Older to move between the runs loaded by the editor. This navigation operates on the latest 100 runs fetched for the workflow. Open the history drawer and scroll when you need an older entry.

​
Star an important run

Use the star action to mark an incident, representative payload, or run you want to find again. Stars are stored with the run and are visible to project members. Starring does not change retention, execution, or billing.

​
Re-run with the same trigger data

Choose Re-run to queue a new run using the selected run’s saved trigger payload.
A re-run is not an exact replay of the historical snapshot. It uses the same trigger data against the workflow’s current saved graph, then creates a new snapshot for that graph. Review unsaved changes and wait for Saved before re-running.
A re-run can also fail immediately when the workflow is paused, the project is out of credits, or billing is invalid. It creates a separate history entry and does not modify the original run.

​
Cancel a scheduled run

Only a run in Scheduled status can be cancelled. Choose Cancel Run from its actions. Cancellation:
  • Changes the run to Cancelled.
  • Prevents the delayed execution from starting.
  • Restores the run credit or usage charge reserved when the run was scheduled.
Pending and Running runs cannot be cancelled from the dashboard.

​
Run history after deletion

Deleting a workflow removes its workflow graph, trigger configuration, event sources, and snapshots. Project-level run records remain for usage tracking and appear as Deleted Workflow.
A preserved run row from a deleted workflow cannot be re-run, and its historical canvas snapshot is no longer available. Deleting the entire project removes its run history.
WorkflowDog currently does not expose a configurable run-history retention setting in the dashboard.

​
Troubleshooting

The workflow runner completed, but at least one node reported an error. Select the run, inspect the red or warning-marked nodes, and read their stored error messages.
This is expected. Re-run preserves the old trigger payload, not the old graph. Use Snapshot (Read-Only) to inspect the original graph and Overlay to repair the current one.
Cancellation is limited to Scheduled runs. A Pending or Running run has already moved beyond the cancellable delayed state.
The snapshot can be unavailable if its workflow was deleted. Check the project-wide history for a Deleted Workflow label.