How-to Guide
Troubleshoot test execution
Diagnose run failures caused by infrastructure or connectivity.
Objective
Diagnose run failures caused by infrastructure or connectivity.
Prerequisites
- Failed run
Procedure
Verify application URL
Confirm target is reachable from execution environment.
Navigation: Console Home quick actions or the project wizard for new initiatives. Use ⌘K / Ctrl+K to jump to any surface.
Verification: Confirm organization and team context in the Console header before making changes.
Check agent status
Agent Console telemetry for online agents.
Navigation: Console Home quick actions or the project wizard for new initiatives. Use ⌘K / Ctrl+K to jump to any surface.
Verification: Note project, run, or agent IDs if you may need support escalation.
Review run logs
Inspect error messages in run detail logs tab.
Navigation: Console Home quick actions or the project wizard for new initiatives. Use ⌘K / Ctrl+K to jump to any surface.
Verification: Confirm UI state matches your runbook. Retry once on transient errors before opening a ticket.
Verification checklist
- Confirm expected UI state or API response after each critical step
- Document run ID, project ID, or agent ID for support escalation if needed
- Notify stakeholders if the workflow affects release gates or production validation
Expected result
Execution succeeds or root cause identified.
Was this page helpful?