Sync problems
Sidebar shows “Last sync failed” Try clicking Sync Codebase again. If it keeps failing, check Configuration → CI / Repos for a connection health warning. Your GitHub connection may need to be re-provisioned or reconnected. “No tests found” after syncing Double-check the Tests directory and Spec file extensions under Configuration → Codebase. Watchtower only imports files that match both. A test I expected to see is missing There are two different reasons a test can disappear from view:- If its title changed in your repository, Watchtower keeps it as an abandoned test rather than deleting it, so your history and comments aren’t lost. Open it from Test Center’s Abandoned filter and use Rebind to a renamed test to reconnect it.
- If its repository was recently unticked as your test source, the test is archived rather than removed. Reselect that repository as the test source under Configuration → CI / Repos and it comes back automatically.
Connection problems
“Something went wrong connecting the repo” This usually means the GitHub App installation didn’t complete, or access to the selected repository was revoked. Go to Configuration → CI / Repos and try Connect GitHub again. I disconnected a repository but it’s still installed on GitHub Disconnecting in Watchtower only stops Watchtower from using that repository; it doesn’t remove the GitHub App itself. Manage or fully revoke access from your GitHub account or organization settings. Unlink/Relink says a permission is missing Opening a pull request requires the Pull requests: write permission on Watchtower’s GitHub App installation; committing directly requires Contents: write. Watchtower checks these before making any change and tells you which one is missing. Update the installation’s permissions on GitHub, or use Dashboard only instead. A direct commit was rejected because the branch is protected Direct commits always target the repository’s default branch. If that branch has protection rules that block direct pushes, use Open a pull request instead, changes made through a pull request go through your normal review process. Watchman isn’t posting reviews Confirm AI analysis is turned on under Configuration → Watchman, and check that the Review Target is set to a destination that’s actually available (GitHub is supported today; Linear is not yet available even though it’s shown in the picker).Patrol problems
A run’s progress bar isn’t moving smoothly For runs dispatched to CI, Watchtower can’t see per-test progress until results are reported back; the progress indicator shows an indeterminate sweep rather than an exact percentage until the first results arrive. Check the console panel for live log output in the meantime. A run shows “No tests ran” This means the suite or grep filter matched nothing, or every matched test was skipped, rather than that the run failed. Check your Test Suite and Grep Filter selections and try again. I can’t find my report after CI failed to upload it The provisioned workflow retries the report upload automatically, and also uploads the report as a workflow artifact namedwatchtower-report (kept for 7 days) regardless of whether the upload succeeded. Open the workflow run on GitHub and download it from the Artifacts section if needed.
I can’t change a test’s status by hand
If a test is controlled by Patrol (tagged AUTO and automated), its status reflects the most recent run and can only change by running Patrol again. This is by design, so automated results can’t drift from manual edits.
”‘<suite>’ is already running”
Only one run per suite can be active at a time. Wait for it to finish, or use Cancel All to stop it and start a new one.