Troubleshoot an Agentic QA run
Open the run from its setup and read How it ended and Coverage. For a reported symptom, open the finding and choose the observation from the run you are investigating.
Run interruptions and coverage#
- Resume a QA run after its environment stops
- Recover when a paused QA run has already ended
- Check why an unknown QA outcome blocks the next run
- Find what a finished QA run kept on disk
- Find why a QA run left a journey unchecked
- Check whether a QA browser step sent a form
- Identify whose access ended a QA run
Sign-ins and live desktops#
- Complete a QA sign-in that needs a person
- Diagnose a QA journey that opened another persona’s account
- Diagnose a QA sign-in with no verified result
- Recover when a QA browser takeover was not acknowledged
- Reconnect to a Level 3 QA desktop
- Diagnose a failed QA desktop readiness probe
Finding history and evidence#
- Open the QA finding observation from a particular run
- Trace a QA finding that reproduced again
- Explain why a QA confirmation was inconclusive
- Check why a QA visual observation was treated as a preference
- Decline or reopen a recurring QA finding
- Share a QA finding report with its evidence links
- Identify QA findings withheld by repository access
GitHub issue filing#
- Locate a QA issue when GitHub filing is uncertain
- Repair a QA filing refused by its GitHub destination