Execution & Results
Execution batches show suite runs, case runs, workflow runs, row-level status, logs, screenshots, videos, and generated artifacts.
Accessing Execution Results
Execution results can be accessed from multiple places in AutoBP. The most common entry point is the suite page, where the execution panel shows recent batches in the sidebar and detailed results in the main area.
You can also view executions from the Dashboard, BP Workspace, and Report Workspace — each showing a list of recent batches relevant to that context.
From a suite page, open the execution panel in the sidebar to see the 10 most recent execution batches.
Expand a batch to see workflows (test cases) and individual row runs with their status.
Click a row run to open detailed results in a dedicated tab, or view quick details in the bottom LogPanel.
For global view, access all recent executions across suites from the Dashboard.
Reading The Result Tree
Every suite launch is grouped into an execution batch. The result tree follows the structure: Batch → Case/Workflow → Row Run. This helps distinguish a broad workflow failure from a single data-row issue.
Each batch displays a summary with total task counts and aggregate status. Expanding a batch reveals its workflows and individual row runs with color-coded status indicators.
Open Execution from the suite, BP workspace, Report Workspace, or Dashboard.
Select the latest batch and expand it to inspect workflows.
Expand a case to see row-level results with pass/fail status.
Open logs, screenshots, videos, downloads, and output artifacts.
Use failure details to decide whether the issue is data, environment, Workday state, or step logic.
Status Meanings
Each execution row displays a status indicator that reflects the current state of the task.
Practical Tips
- Queued — waiting for its turn in a serial execution chain.
- Running — actively being executed by the runner (server or local).
- Done — completed successfully with no errors.
- Failed — completed with an error that needs investigation.
- Cancelled — stopped by a user or system guardrail.
- Partial — some rows passed, some failed within a batch.
- Local variants (local_pending, local_running, local_queued) indicate execution on a local runner machine.
Execution Detail View
Opening a row run from the batch tree opens the full execution detail view with four tabs providing comprehensive diagnostics.
**Console tab**: Left panel shows a video recording player synchronized with logs; right panel shows real-time system log stream with timestamps. Click any log entry to seek the video to that moment.
**Steps tab**: Filterable list of all steps executed (all/pass/fail), with expandable cards showing error context, action-level logs, and screenshot evidence for each step.
**Screenshots tab**: Grid of all screenshots captured during execution. Click any screenshot to view it full-size.
**Accessibility Tree tab**: JSON view of the page accessibility tree captured at the final execution state — useful for debugging DOM-related failures.
Click any row run from the batch view to open the execution detail tab.
Use the Console tab to replay video alongside log entries for visual debugging.
Switch to the Steps tab to see which individual steps passed or failed.
Inspect screenshots to understand page state at failure points.
Use the Accessibility Tree for deep DOM debugging on complex pages.
Practical Tips
- The video player syncs with logs — click any log line to jump the video to that point in time.
- Use the step filter to quickly isolate failed steps in large workflows.
LogPanel (Bottom Panel)
When viewing a suite, selecting a row run from the sidebar opens the LogPanel at the bottom of the suite page. This provides a quick overview without switching to a dedicated tab.
The LogPanel includes a video player, screenshots gallery, accessibility tree viewer, real-time log stream, and error details for failed tasks.
Rerun Strategy
Failed executions can be rerun at different levels depending on the nature of the failure. The Rerun button is available in both the LogPanel and the detail view.
Rerun a single row when the data was corrected — this reruns only that one data row within the case.
Rerun an entire case when step logic changed — all rows of that case will execute again.
Rerun the entire suite only after environment or shared setup issues are fixed.
Practical Tips
- Always check the first failing row before reviewing later failures in the same batch.
- Do not immediately rerun an entire failed batch — diagnose first, then rerun the smallest useful unit.
AutoFix
For failed steps, AutoFix provides AI-powered fix proposals. When a task has failed, an "AutoFix" button appears in both the LogPanel and the execution detail view.
Click "AutoFix" on a failed task to send the error, step code, and DOM accessibility tree to the AI.
Review the proposed fix in the diff viewer — it shows the step name change or code modification.
Click "Apply Fix" to save the fix directly to the step definition.
Rerun the row to verify the fix resolves the issue.
Practical Tips
- AutoFix works best for selector failures, timeout issues, and assertion mismatches.
- Always review the proposed fix before applying — AI suggestions should be treated as drafts.