Runs and Execution History
The Runs workspace is where ASAPilot turns automation status into proof. It is the place to inspect what actually executed, what it returned, and why a workflow failed or stayed queued.
Primary controls
- • Search by run ID, automation name, summary text, or error text.
- • Filter by automation so one noisy workflow does not hide the rest of the queue.
- • Use status chips to isolate queued, running, succeeded, or failed runs.
- • Select any run to inspect summary, markdown output, runtime metadata, and payload context.
Run list and queue visibility
The left rail shows total runs, visible runs, failed runs, and the active queue count so operators can see whether work is stuck or simply still in flight.
Run detail
The detail view exposes status, timestamps, duration, summary text, findings count, error message, and markdown output for the selected automation run.
Payload context
Runs include input and output payload JSON where available, which makes this page useful for debugging automation behavior rather than relying on vague status labels.
How to use Runs well
- Start with failed runs if the dashboard feels stale or an automation result looks suspicious.
- Read the markdown summary first, then inspect payload JSON only if the summary is missing, vague, or contradictory.
- Use the automation filter when reviewing a rollout, because mixed run histories hide regressions.
- When you want to execute again, go back to Automations or Home and use the run-now control there.
SEO page for run history
Use the commercial-intent page when you need the feature explained for buyers or search traffic.
Create better runs
Go back to Automations if the problem is the workflow definition, schedule, or scope.
Return to Home
Use Home to understand which recent run matters before opening the full execution record.