Start with the target environment, then check credentials, then inspect the evidence. Most failures come from the run targeting the wrong URL, missing preview access, stale test data, or broad assertions.

Preview URL unavailable

Move the Autonomy step after the deployment step and confirm the preview URL is exported into the CI environment.

Use high-entropy generated passwords and verify that the inbox domain is accepted by the auth provider.

False pass on intermediate form

Add a final-state check that rejects active signup, password, OTP, or payment forms.

Pull request comment missing

Verify the GitHub App installation, pull request number, repository permissions, and whether the run completed before the workflow exited. For comment-triggered runs, the commenter must be an owner, member, or collaborator on the repository — comments from bots are ignored.

GitHub check is red but nothing failed

A neutral conclusion means the command was rejected — unparseable, ambiguous, over the fan-out limit of 8 runs, or unauthorized. Read the comment body for the reason. Only failure and timed_out reflect a run outcome.

Autonomy picked the wrong environment from a comment

Target precedence is: explicit URL, then named environment, then PR preview, then branch match, then repository default, then workspace default, then the case's own default. Pass url: or env: in the comment to override everything below it.

Hosted recording session never goes live

A hosted session runs in Autonomy's infrastructure and cannot reach localhost, a private IP, or a VPN-only host. Record against a preview or staging URL.

Visual comparison mismatches on every run

Check the viewport first — a desktop reference compared against a mobile capture is a total mismatch by definition. Then widen the tolerance one level, or narrow the reference from a full page to the component under test.

Figma reference will not resolve

The URL must include a node-id; copy the frame link from Figma rather than the file URL. If the token was rejected, generate a new personal access token and re-run Test connection before saving.

API assurance reports indeterminate

Indeterminate means the evidence could not prove the contract either way — usually an unresolved or depth-limited schema branch, or network capture the platform could not observe reliably. Treat it as unknown, not as a pass.

Mobile run reports that mobile testing is unavailable

iOS and Android execution are disabled by default while device runner support is completed. Build upload still works; contact us to have mobile execution enabled for your organization.

Network assertion fails

Open the request evidence for the failing step. Confirm the target environment, auth state, request timing, and whether the backend side effect is eventually consistent.

Mobile artifact not found

Confirm the CI job produced the artifact, the upload step references the correct path, and the artifact matches the platform selected for the run.

Troubleshooting