Review your first run

For a background execution, open the View link returned by the QA Agent or open the Run from Runs. For an agent Live View execution, review the inline result in its card; that mode does not save a Runs history entry.

Inspect the result

Start with status and execution counts. A Passed Run with zero executed cases does not prove the workflow works. Then inspect the source case or plan, trigger, timing, individual case outcomes, failed reason, linked Issues, and recording when available.

Results and recording availability are separate. If the recording is still Processing, refresh later. See Run evidence.

Decide what to do next

If the intended case passed and its result supports the expected behavior, keep it as your first verified check. Continue with Build regression coverage to grow a small suite.

For failures, use the reason and recording to distinguish:

• Product regression: Expected behavior is broken in the tested environment.
• Stale instructions: The case describes an older UI or behavior.
• Bad test data: The account, workspace, or record state no longer fits the case.
• Environment issue: The app, deployment, or dependency is unavailable.

A failed background execution with an issue report can create or link an Issue automatically. Review that report before creating a duplicate. Edit the case when instructions are stale; rerun once you understand the result or have changed the relevant state. Reruns consume credits and use current settings.