Troubleshooting

A repository is missing from the list

It was almost certainly not included when the App was installed. The repository list is controlled in GitHub: open the App's configuration there, add it, and it appears in Monterva. You do not need to reinstall.

Settings says the connection is disconnected or suspended

Someone removed or suspended the App in GitHub. Monterva is told and updates the page.

• Suspended — un-suspend it in your GitHub settings and reviews work again.
• Disconnected — the App was removed. Connect GitHub again.

Your existing reviews and findings are unaffected either way.

A review failed

The audit page states the reason in plain language. The common ones:

• The branch no longer exists. It was deleted or renamed after the review was queued.
• We could not read the repository. Access was removed or narrowed while the review was waiting.
• The archive was refused. The snapshot contained something our unpacking rules do not allow. This is rare and worth telling us about.

Failures worth retrying are retried automatically. Ones that will produce the same answer again are not, so that you find out promptly rather than three minutes later.

A review is stuck

Reviews that stop making progress are detected and returned to the queue automatically, so a review that appears stalled will usually resolve itself. If one stays in the same state for much longer than others of similar size, tell us.

The report says a language was not covered

That is the coverage section doing its job. Monterva analyses the languages its tools support and names the ones it cannot, rather than leaving you to assume everything was read. It is a statement about our coverage, not about your code.

A finding looks wrong

Mark it false positive. That records your judgement without changing the finding's severity, confidence or evidence, which stay as the analysis produced them.

If a whole rule is producing noise in your codebase, tell us — that is a signal about the rule rather than about you.

A finding you have deliberately accepted keeps coming back

Monterva does not read your repository's own suppression files, so a rule you disabled there is still reported. Mark the finding ignored in Monterva instead; that decision belongs to your workspace and survives future reviews.