Using OpenMerge

Troubleshooting

What to check when a review does not appear or needs attention.

No review appeared

Work through these checks in order:

  • The repository is selected in the GitHub App installation, and it appears on the Repositories page. If not, update access in GitHub and click Sync from GitHub.
  • Auto-review is switched on for the repository.
  • The GitHub App installation is not suspended.
  • The pull request was opened, reopened, or received new commits. Editing the title or description, commenting, or requesting a review does not start one.
  • The same commit was not already reviewed. Push a new commit to review the latest code.

Review needs attention

OpenMerge already retried the review automatically before showing this status. Open the review from the Reviews page to read the last error, then push a new commit or close and reopen the pull request to try again.

Review seems stuck

Reviews show Queued, Reviewing, or Retrying while work is in progress, and the dashboard refreshes on its own. Large pull requests take longer. If a worker stops mid-review, the review is recovered and queued again automatically.

Self-hosting?

Check that the worker process is running and can reach Redis and PostgreSQL. Reviews stay queued while no worker is available. See Self-hosting.

Fewer comments than expected

This is by design. Duplicates are dropped and each review posts at most 12 comments, highest severity first. The security agent also skips problems that existed before the pull request. The summary and the review detail page show everything that was posted.

Session expired

Dashboard sessions last seven days. When yours expires, the dashboard shows a Sign in with GitHub button. Signing in again does not affect reviews, which keep running whether or not you are signed in. The API reports this state as INVALID_TOKEN or TOKEN_REQUIRED.

Something unclear or out of date? Open an issue.