The Runs screen records workflow executions and lets you open a run’s details. Use its status views and workflow filter to locate an execution, then review the saved timing and node log before deciding what to change.
Open the Runs screen
- In the WordPress dashboard, open Agent Workflows → Runs.
- Use the status links above the table to choose All, Queued, Running, Success, Failed, or Partial.
- To narrow the results to a workflow, use Filter by workflow and choose the workflow name. The list refreshes to show its runs. Select Clear filter to remove the workflow filter.
- Use the table pagination to browse older entries in the current results.
Screenshot to add: [Runs screen with status views and workflow filter]
Find the run and read its status
The table shows these columns:
- Run: The run ID. Select the ID or its View action to open the details.
- Workflow: The workflow associated with the run.
- Status: The run’s current or final status.
- Attempt: The attempt number for this run in a retry chain.
- Started: The start time, or Not started yet if execution has not started.
- Duration: The recorded run duration. A queued run may not have a duration yet.
Understand the status
- Queued: Waiting for background execution or a scheduled retry.
- Running: Execution is in progress.
- Success: The run finished successfully.
- Failed: No nodes succeeded before the run failed.
- Partial: At least one node succeeded, but the overall run did not finish successfully.
A status is a summary, not a replacement for the node log. Open a failed or partial run to find the node message and any saved input or output details. A Success run status also does not mean an external service accepted every business outcome you expected; check the recorded node results and the response fields for that action.
Review Run Details
- In the Runs table, select the run ID or choose View.
- On Run Details, review Workflow, Status, Attempt, Started, Finished, and Duration.
- If a trigger payload was saved, expand Trigger payload to inspect the formatted JSON.
- In the Node log table, look for the first relevant Error or Skipped entry and read its Message. Choose View in the Details column to inspect available Input and Output data.
- Use the recorded node details to correct the workflow configuration or downstream mapping, then run a new test if appropriate.
Screenshot to add: [Run Details screen with node log]
Re-run or delete a run
For runs with status Success, Failed, or Partial, the list offers a Re-run action. The details page offers Re-run this workflow. This creates a new run linked to the earlier run and reuses its saved trigger payload. It does not resume from the failed node. Nodes that succeeded earlier may run again, so check for actions that could create duplicate records, messages, or external requests.
Runs that are still Queued or Running do not offer a re-run action. To remove history manually, use the row’s Delete action or select multiple rows and use the bulk Delete action. Deletion is permanent and removes the selected run’s recorded history; do not delete a run if you still need its diagnostic details.
Understand automatic retries and missing history
When background execution is enabled, the plugin may create a new queued attempt after a failed or partial run if its node error message matches a recognized temporary-failure signal. It allows up to three attempts in total. Each retry starts the workflow again from the beginning and uses a separate run record; it does not resume at the failed node. Manual Re-run is synchronous and is not automatically retried.
Finished history is kept for 14 days by default. To change this, open Agent Workflows → Settings → Logging & Retention and edit Keep finished run history for. A value of 0 keeps history indefinitely. The daily cleanup removes older finished runs and their node logs; Purge Now runs the cleanup immediately. If a run is missing, check the selected workflow and status filters, then check whether retention or a manual deletion removed it.