A pull request wasn’t reviewed automatically The HeyDeer Review check on the latest commit says why, titled Review skipped or, with Fail the check when issues are found on, Review required. No check? See No HeyDeer Review check appears .
Likely cause What to do Review schedule is Manual only, the default for new workspaces. Choose Once per PR or On every push. See Automatic reviews . The pull request doesn’t match your Automatic review filters, which skip drafts and forks by default. Mark it ready, change the filters , or comment @heydeer review. Automatic reviews are paused on this pull request. Comment @heydeer resume. Once per PR already started a review, or one is still queued or running; or the pull request reached Maximum automatic reviews per PR. Comment @heydeer review. The workspace ran out of credits or reached its usage limit. Add credits, or raise the limit in Spending controls, then request a new review. See Auto-reload and usage limits . On the trial, the repository already had a trial in another workspace. Choose a plan , then request a review. The GitHub App can’t reach the repository. Check Organization settings → GitHub connection. See GitHub app and permissions . HeyDeer waits about 30 seconds after a push, or the review is queued (Review queued). Wait. The commit already has a review; relabeling or reopening doesn’t repeat it. Push a new commit, or comment @heydeer review.
The check failed or the review didn’t finish Check title Cause What to do Review found issues that need attention Issues were found with Fail the check when issues are found on. Fix the issues and push, or resolve the findings. Review incomplete A repository check or an earlier finding wasn’t assessed. Request another review. Review could not run The base branch has an invalid .agents/checks configuration. Fix it, then request a review. Review could not run The PR discussion is too large: over 200 review threads, 1,000 comments in a thread, or about 180 KB. Continue in a new pull request. Review could not run GitHub or HeyDeer was unavailable. Request the review again. Review failed, Review timed out The review didn’t complete. Failures on HeyDeer’s side are refunded. Request another review. Review cancelled Someone canceled the review, its pull request closed, or a newer push replaced it (On every push). Request another review. No reviewable files Every changed file is out of scope, such as generated files. Nothing to do.
All conclusions are listed in The HeyDeer Review check .
No HeyDeer Review check appears Likely cause What to do Publish GitHub check is off for the repository. Turn it on. See Publishing results . The repository is on Manual only and has never been reviewed. Request a review. Later revisions then get a check. The GitHub App lacks Checks: Read and write, or the repository isn’t in its installation. Approve the permission or add the repository on GitHub. The pull request is closed. Reopen it.
A command got no reply or an error Likely cause What to do No reply: the comment holds more than the command, the command was added in an edit, or a bot posted it. Post a new comment with only the command, from a personal account. No reply: the GitHub App lacks Issues read permission. Approve it on GitHub. You lack write access, or aren’t in Who can manually trigger reviews. Ask an admin, or someone who has access. Too many requests, or the review queue is full. Wait, then post the command again. pause or resume on a closed pull request.These work only on open pull requests. Not enough credits, or the usage limit is reached. Add credits or raise the limit, then post the command again. GitHub was unavailable. Post the command again in a new comment.
HeyDeer doesn’t answer questions. See PR comment commands .
The review shows a warning Each warning turns off automatic approval for that review.
Warning What to do Over 10 checks matched; only the first 10 by file name ran. Narrow the patterns or rename files. See Repository checks . The pull request changes .agents/, and the new check configuration is invalid. Fix it before merging, or reviews on that branch stop. Lower-confidence findings were left out; a review keeps at most 30. Address the findings shown, then request another review. Some findings or thread assessments were incomplete. Request another review.
A rule or check seems ignored Likely cause What to do The check changed in this pull request; HeyDeer reads the base branch’s version. Merge the change first. The check’s patterns match no changed file, or the file isn’t a .md file directly in .agents/checks/. Fix the patterns or move the file. See Repository checks . The AGENTS.md rule is in a directory that doesn’t cover the changed files. Move it. See AGENTS.md . Instructions were saved after the review was requested, or repository instructions override them. Request another review, or resolve the conflict. See Review instructions . The finding was below the Feedback scope. Try Balanced or Detailed. See Feedback scope . The file is marked linguist-generated in .gitattributes. Remove the attribute. See What HeyDeer reads . The rule can’t be judged by reading the code. Rewrite it as something visible in the diff. See Writing effective checks .
MCP server errors The form explains each rejected value; see MCP servers . After changing an endpoint, enter a new token or remove the saved one. Only workspace admins who own the GitHub organization or account can manage servers.
Signing in and GitHub access Likely cause What to do Your GitHub sign-in expired, and HeyDeer shows Sign in with GitHub. Select it to sign in again and return to the same page. You’re signed in with a GitHub account that can’t see the review or organization. Select Continue with GitHub or Reauthorize GitHub, then choose the right account on GitHub. An organization or repository is missing when you connect. Under Organization or repository missing?, check the installation, sign in through SSO on GitHub if needed, then select Reauthorize GitHub. See GitHub app and permissions .
Billing problems Likely cause What to do The card was declined, or your bank asked to verify the payment. For a subscription payment, select Complete payment in Usage & billing → Overview. For other purchases, use another card. Add credits says you need a plan. Choose a plan first, or select Complete payment if Overview shows it. See Plans and add-on credits . Auto-reload is Off, with a reason below it. Fix the cause, then turn it on again. See When a reload fails . Renewal payment pending. Your plan stays active meanwhile. If the payment failed or needs your bank’s confirmation, HeyDeer emails the workspace; select Complete payment. Add credits or auto-reload says the 24-hour limit is reached. Wait until the rolling 24-hour purchase limit has room, or contact support. Payments and new paid reviews are paused. HeyDeer is resolving a billing issue with the workspace. Contact support. A payment is still processing, or Add credits asks you to check an earlier purchase. Select Check purchase until it shows the result. Don’t start another purchase.
Still stuck? Email hey@heydeer.ai with a link to the pull request or review. Never include tokens or card numbers.
