> For the complete documentation index, see [llms.txt](https://docs.aviator.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aviator.co/flexreview/how-to-guides/troubleshoot-reviewer-assignment.md).

# Troubleshoot Reviewer Assignment

Find and fix issues with automatic reviewer assignment in FlexReview using this troubleshooting guide.

## A reviewer is not assigned to a PR

Make sure you have read the [whitelist Teams](/flexreview/how-to-guides/whitelist-teams-for-review-assignment.md) for reviewer assignment. The most common reasons why a reviewer may not be assigned:

1. Do you use a CODEOWNERS file? FlexReview currently requires presence of a CODEOWNERS or an `.aviator/OWNERS`file to suggest reviewers.
2. Is FlexReview global enabled for this repository? From the menu, go to Repositories and check the FlexReview status for the repository. Enable it if it's not already enabled. It may take a few minutes for Aviator to index the pull request data after enabling FlexReview global config.
3. Are the right teams enabled? Even after the global config, FlexReview requires each team to be separately enabled as well. Go to Teams section, and select your GitHub Team from the dropdown. See if this is enabled. Make sure at least some of the modified files in the pull request are owned by this team.
4. Are the authors whitelisted? This is enabled for everyone by default. Go to FlexReview configuration (Repositories > FlexReview status > Configure) for the given repository, make sure that the list of GitHub users here include the team or the user who authored this pull request.

## No owners / unowned files

There may be a scenario where no CODEOWNERS path matches the files that are modified. These files are considered unowned. In the scenario where all files in the pull request are unowned, Aviator will not assign any reviewers.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.aviator.co/flexreview/how-to-guides/troubleshoot-reviewer-assignment.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.