PR Review Didn't Run
What to check when the GitHub App's review doesn't appear on a pull request.
When the GitHub App is set up, each pull request gets a Thruline check run within a minute or two of opening. If you don't see one, work through these steps.
Step 1: Is the app installed on this repository?
On the repository's (or organization's) Settings › GitHub Apps page, confirm Thruline is listed and this repository is in its install scope. If not, install or extend it at github.com/apps/thruline-context-pr-review-app.
Step 2: Read the check run's title
When Thruline can't review a pull request, it still posts a neutral check run, and the title names the reason. It is never a failure — a blocked review doesn't fail your build.
| Check title | What it means | What to do |
|---|---|---|
| Thruline account needed | The App is installed, but the account that installed it doesn't have Thruline yet. | Follow Set Up to create an account and connect the repository. |
| Thruline plan required | The owner has an account but no active plan. There's no free tier, so the repository can't be indexed or reviewed. | Start a free trial or subscribe on the pricing page. |
| Repository not indexed | The plan is active; this repository just hasn't been indexed yet. | Ask your editor to run thruline_index with the owner/repo name. If indexing is failing, see Indexing Stuck. |
| PR-review quota reached | The plan's monthly PR-review allotment is used up on a plan that doesn't bill overage. | Upgrade from your plan page. See Rate Limits. |
Each of these links to the page that resolves it from the check's Details button as well. Thruline account needed and Thruline plan required are also posted as a pull request comment, in the place a review would normally appear — both are onboarding steps only you can take. The comment is updated in place on each push rather than repeated, and becomes the review itself once the repository is indexed under a plan.
Step 3: Did the webhook fire?
In the GitHub App's installation settings, open Configure › Recent deliveries and find the pull_request event for your PR.
- No event listed — GitHub didn't deliver it. Usually the install scope doesn't include the repository, or the action wasn't
opened,synchronize, orreopened(for example,editeddoesn't trigger a review). - Event listed with a response — click into the delivery to see the status:
| Response | Meaning |
|---|---|
401 | Signature verification failed. This is an internal issue; contact support with the delivery ID. |
200 | Thruline accepted the event. If no review appears, retry with a new commit (Step 4). |
Step 4: Retry with a new commit
Pushing a commit to the pull request fires another synchronize event and re-runs the review, which clears most transient failures. If the retry still produces no review, contact support through the feedback page with the PR URL, the webhook delivery ID, and the repository's index status.
Other things to know
- Draft pull requests are reviewed the same as any other pull request.
- Branch protection. If a required Thruline check never appears, the pull request can't merge. Make sure the app is installed and the repository is indexed, then push a commit to re-trigger the check.
- PR-review limit. On paid plans, reviews continue past the monthly allotment as overage rather than stopping, so the quota check above only appears on plans without overage. See Rate Limits.