> ## Documentation Index > Fetch the complete documentation index at: https://docs.coderabbit.ai/llms.txt > Use this file to discover all available pages before exploring further. # Troubleshooting Triage > Why Triage will not open, why the queue is empty, why an action is refused, why a card looks out of date, and the limits you can actually hit. export const OpenBetaBadge = ({tip = "This feature is currently in open beta. We are actively improving it based on your feedback. If you encounter any issues or have suggestions, please share them on our Discord community or visit the support page.", title = "Open Beta", cta = "Contact support", href = "/support", disabled = false}) => { return {title} ; }; export const TeamPlanBadge = ({tip = "This feature is available on Team (formerly Pro+), Advanced, and Enterprise. Please refer to our pricing page for more information about our plans and features.", title = "Team Plan", cta = "Read more", href = "https://coderabbit.ai/pricing", disabled = false}) => { return {title} ; }; export const GitLabBadge = ({tip = "This feature is available on GitLab.", title = "GitLab", cta, href, disabled = false}) => { return {title} ; }; export const GitHubBadge = ({tip = "This feature is available on GitHub and GitHub Enterprise.", title = "GitHub", cta, href, disabled = false}) => { return {title} ; }; | ## When Triage will not open Triage names the specific requirement you are missing rather than showing a generic error. Match the message you see: | Message | What it means | What resolves it | | - | - | - | | Triage is not enabled for this organization | Triage has been switched off for your organization. | Contact [support](mailto:support@coderabbit.ai) to ask about access. | | No active subscription found | The organization has no active subscription. | Check [Subscription management](/management/subscription-management). | | Invalid subscription | The subscription cannot be interpreted. | Contact support; this is not something you can fix from the app. | | Triage requires membership in this organization | You are signed in, but not a member of the organization you are trying to view. | Ask an organization admin to add you. | | Triage requires a workspace-backed organization | The organization is not backed by an active CodeRabbit workspace. | An admin needs to complete organization setup. | A few of these messages name the feature `Queue`; they are about Triage. If your organization's plan is below Team, Triage does not open. Upgrade to Team or higher — see [Plans](/management/plans). Opening Triage also requires an active Review seat. If your organization meets every requirement above but Triage still does not open for you, ask an admin to assign you a seat — see [Seat assignment](/management/seat-assignment). Two more, which are about your session rather than your organization: * **"Your session isn't valid for this organization"** — sign in again. If that does not help, your access to the organization may have been removed. * **"You don't have access to Triage"** — your account does not meet one of the requirements above. An organization admin can check the plan and your membership. ## The queue is empty An empty queue is usually correct. Triage tells you which kind of empty it is: | What you see | What it means | | - | - | | **Connect a repository to get started** | No repositories are connected to CodeRabbit yet. This is the only empty state with a button — use it. | | **No matching pull requests** | Your search matched nothing. Clear the search box. | | **No pull requests match these filters** | Your filters are too narrow. Use **Clear filters**. | | **Your inbox is clear** / **No open PRs of yours** / **No reviews assigned** / **No close candidates** | There genuinely is nothing in that view right now. | | **No open pull requests** | Nothing tracked and open across your repositories. | If you expect pull requests that are not there, check the two scoping rules: Triage shows only repositories your signed-in Git provider account can access, and it excludes archived repositories. ## A card looks out of date Cards are Triage's stored view of your pull requests, not a live provider query, so a card can lag your Git provider briefly. Triage repairs this on its own: * When cards render, Triage quietly re-reads live provider state for the rows on your screen and corrects them. * Coming back to the tab triggers the same repair, at most once every ten minutes. There is no continuous polling and no refresh button, and a repair that is skipped — because it is already running, or because too many have run recently — is silent. If a card's state matters right now, **open the check panel**, which reads the provider when you open it, or open the pull request. A card also carries only one freshness timestamp for fields that arrive from different places at different times. A recent timestamp means something on the card was updated recently; it does not mean every field was. ## A signal disappeared from a card Signals that describe a specific reviewed commit are withdrawn when the author pushes a newer one, rather than shown against code they no longer describe. Change type, issue severity, blast radius, and security risk come back after CodeRabbit reviews the new commit. See [Signal freshness](/triage/your-triage-view#signal-freshness). ## An action is disabled or refused | What you see | Cause | | - | - | | Refused for a missing Review seat | Opening Triage, and every action that writes to your provider or spends model capacity, needs an active Review seat. See [Seat assignment](/management/seat-assignment). | | The action is missing entirely on this card | It does not apply to this pull request right now — there is nothing to repair, or Triage cannot act on it directly. The card offers a link to your Git provider in that case. | | A prompt to reconnect your Git provider | Your provider authorization is missing, expired, or lacks required permissions. On GitHub, SAML-SSO approval may also be required. Reconnecting is a deliberate full-page redirect that returns you to the same filtered view. | | A merge is refused | Someone pushed to the pull request after the card was built, or your Git provider no longer considers it ready: checks stopped passing, it has conflicts, you lack permission to merge, or a branch protection rule blocks it — including a rule that requires the branch to be up to date with its base. Review it and try again, or open the pull request in your Git provider. | | The close is refused as no longer eligible | The pull request has changed since the card was built — it may already be closed or merged. Triage refreshes to show you the current state. | | Rate-limited | You or your organization has made too many provider requests. Wait and retry. | ### Closing did not work If the comment posted but the close failed, Triage keeps the posted comment visible but locks it from editing. Select **Retry close** in the same confirmation box; Triage skips reposting the comment. ### Setting a priority failed If the pull request was re-evaluated while your board was open, saving a priority fails and asks you to refresh and try again. That is deliberate — it stops you from overwriting a value you could not see. Reload and set it again. Selecting **Close candidates** requires a reason of up to 200 characters and a pull request that is still tracked and open. The reason cannot be empty or contain only spaces. If the pull request has closed or merged, refresh the view instead of retrying the selection. Remember that a manual priority **cannot be cleared** once set. Choosing **P0**–**P3** removes the close recommendation; choosing **Close candidates** saves a manual recommendation and its reason. ## A Slack message did not arrive Reviewer pings and digests need a chain of things to be true. Triage names the broken link: | What you see | What it means | | - | - | | **Slack connection is inactive** / **Slack delivery isn't configured** | The workspace has no usable Slack installation. See [Slack connections](/slack-agent/connections). | | **Slack mapping is missing** | The reviewer's Git provider account is not linked to a Slack account. | | **Slack mapping couldn't be resolved safely** | More than one Slack account could be that reviewer. Confirm the right one and retry — Triage will not guess. | | **Reviewer notifications are off** | That person has turned reviewer notifications off. | | **Slack notification isn't supported** | Reviewer notifications are not available for that Git provider. | | **Notifications are not set up** in Follow settings | Your own Slack identity is not linked yet. | | No digest at all | You had nothing waiting. Triage does not send an all-clear message. | ## An automation rule did not run Open [Triage settings](https://app.coderabbit.ai/triage/settings), check the rule's status, and inspect its activity and per-PR outcome. A matching condition alone does not mean the action is eligible. | Symptom | What to check | | - | - | | Saved rule did nothing | Saving a rule does not enable it. Enable future automation or explicitly confirm eligible existing PRs for merge, close, or Slack actions. | | Existing PRs were not acted on | Already-matching PRs are not automatically enrolled. Use preview and confirmation for merge, close, or Slack rules. Auto-fix requires new relevant activity after enablement. | | Auto-fix has waited longer than expected | Code changes, feedback, reviews, and CI updates, including relevant bot activity, reset its inactivity clock. Check for activity after the latest enable, edit, or resume, and allow for available repair capacity. | | A condition is unknown | Its evidence is missing, incomplete, stale, or refers to an older commit. Wait for current evidence; unknown does not mean safe to act. | | Merge is waiting | Check required reviews, checks, branch protection, the current commit, integration permissions, and whether GitHub has queued the merge. | | Close did not happen after notice | Relevant activity or a changed PR can cancel the pending close. The waiting period starts only after the notice is posted. | | Slack reminder did not arrive | Check the Slack connection, identity mapping, recipient notification preferences, delivery time and timezone, quiet hours, and cooldown. | | Rule paused itself | Inspect the reported access denial or repeated failures. Repair the integration or permissions before resuming. | | Saving or enabling reports a conflict | Narrow overlapping scopes or conditions, or pause the incompatible rule. | | Result is uncertain | CodeRabbit is still establishing what the provider did. Check the provider and history before requesting another action. | See [Triage rules](/triage/rules) for the complete activation and action behavior. ## Limits | Thing | Limit | | - | - | | Saved views per person, per organization | 50 | | Saved view name | 100 characters | | Repositories selected in one filter | 50 | | Authors, reviewers, or projects selected in one filter | 100 | | Search or title text | 255 characters | | Repositories your GitHub account can access | 5,000. Above that, Triage refuses to build your queue rather than showing a partial one. | | Cards per page in list layout | 100 | | Cards per group in board layout | 20 | ## What's next Re-check the plan, provider, and membership requirements for opening Triage at all. See what each action needs before you use it, including seats and provider support. Widen a view or clear a filter when the queue is emptier than you expect. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.