---
title: "Troubleshooting"
description: "Find the cause of an incomplete check and get the right next action."
canonical_url: "https://coldvisit.com/docs/troubleshooting"
md_url: "https://coldvisit.com/docs/troubleshooting.md"
last_updated: "2026-09-12"
---

# Troubleshooting

Find the cause of an incomplete check and get the right next action.

## Start with the run

Open the run from Home. Failed means the journey produced a failing result; couldn’t run means ColdVisit did not establish a conclusive result. Inspect the coverage list to see which flows ran, were not affected, or were inactive.

## Preview or sign-in problems

In Settings, open the affected repository’s setup. Confirm the detected preview URL and reverify any protected-preview bypass token. Refresh expired credentials or a saved session under Test accounts; the account becomes ready only after browser verification.

After fixing access, open the flow and use Run now against the confirmed preview. A manual run has its own identity and does not update a PR check.

## A changed interface

If a selector proposal is available, compare its current and proposed locators with the recorded browser evidence. Accepting checks that the approved script has not changed and that the repair still passes guardrails.

For a journey that changed intentionally, create a candidate revision. The active flow stays intact while the candidate is authored. Review both sets of steps before replacement; the new revision starts with a closed write boundary.

## Missing coverage or evidence

Confirm that both the flow and its repository gate are enabled. A plan change can suspend excess flows while retaining their history. Pin flows in advance to express which coverage should survive a downgrade.

Video and screenshots are available only when recorded and uploaded successfully. Sign in with access to the owning installation to open evidence links, including links from GitHub. A missing recording is not evidence that the application passed.