> ## Documentation Index
> Fetch the complete documentation index at: https://support.metaview.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Application Review FAQs & Troubleshooting

> Fixes for candidate counts that don't match your ATS, unparsed CVs, stuck evaluations, and rejection email problems.

This page collects the problems people hit most often when running Application Reviews, and how to resolve them. For how Application Review works end to end, see the [Application Review Overview](/application-review/overview) and [Application Review Setup](/application-review/application-review-setup), and [Application Review Best Practices](/application-review/ai-best-practices-app-review) for guidance on writing ICPs and using the product responsibly.

## Candidates and evaluation

### My candidate count doesn't match my ATS

It's normal for the number of candidates in an Application Review to differ from the number you see in your ATS. Common reasons include:

* **Stage and role scope** — a review pulls candidates from one specific stage of one role. If you compare it against a different stage, or your ATS's whole-pipeline view, the totals won't line up.
* **Merged duplicates** — when the same person applies more than once, Metaview merges them into a single candidate.
* **Multiple applications from one person** — a candidate with several applications is counted once.
* **Anonymised candidates** — candidates whose personal data has been anonymised in your ATS (for example, after a data-retention period) aren't synced, so they don't appear.
* **Restricted or confidential candidates** — private, confidential, or otherwise restricted candidates in your ATS aren't synced.
* **Sync timing** — new applications and recent changes in your ATS can take up to \~30 minutes to be reflected in Metaview.

<Note>
  These differences are expected and don't mean candidates are missing. If your numbers still look off after accounting for the above, contact support with the role name and workspace so the team can take a look.
</Note>

### A candidate shows as **Inconclusive** but they have a resume

This usually means the uploaded file could not be parsed. Common causes include corrupted PDFs, image-only scans with no text layer, or unusual file formats. Open the CV tab to view the original files. If the file looks normal to you, flag it to support so the team can investigate.

### Evaluation seems stuck or is taking a long time

Each review version goes through a lifecycle: **Draft** (ICP being written), **Evaluating** (candidates being assessed), **Active** (evaluation complete, ready for your review), and **Archived** (replaced by a newer version).

For large candidate pools, the Evaluating phase can take longer than usual. If a review has been stuck in this status for more than 30 minutes, contact support with the role name and workspace so the team can check for processing issues.

## Setup and roles

### Why can't I reject or progress candidates?

Your ATS API key likely does not have the required POST permissions. See [ATS Setup](/application-review/application-review-setup#ats-setup) and check that the Advance Application and Reject Application permissions are enabled on your ATS API key.

### Why do I see closed or irrelevant roles during setup?

Application Review should only show open roles from your ATS. If you are seeing closed or archived roles, try refreshing the page. If the issue persists, contact support.

### Can I make changes to an Application Review after it's been created?

Click the `…` (3 dots) menu next to the Application Review you want to update, then select `Edit`. From there, you can give it a new custom name and update certain settings like the import applicant stage, default rejection reason, and rejection email.

### How can I check which job posts an Application Review is linked to?

Click the `ATS logo` button in the Application Review toolbar, next to **Credits**, to see the job posts linked to the review. You can click any listed post to open it in your ATS.

## Rejection emails

### The rejection email came from the wrong person

The sender is determined by your ATS, not by Metaview. In Greenhouse, update the sender in the rejection email template settings. In Ashby, rejections are sent from the system no-reply address and cannot be changed from within Metaview.

### When are rejection emails sent?

Rejection emails are sent automatically on a weekday morning, within two days of the status change. The timezone used for send timing may vary depending on your ATS. This timing is not customizable at this time. See [Rejection emails](/application-review/application-review-setup#rejection-emails) for more detail.
