> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/application-security/code-security/application-security-scans-management/manage-scans-through-the-tenant-ui/pull-request-scans/references/reference-d-pr-status-values.md).

# Reference D: PR status values

PR status reports the policy evaluation result and determines the merge outcome. It applies to pull request scans and CI scans. Branch periodic scans have no scan status.

| PR status       | Meaning                                                                                                          | Merge consequence                                                                              |
| --------------- | ---------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- |
| **Passed**      | The scan completed and no policy violation was detected                                                          | The status check reports success and the merge proceeds                                        |
| **Failed**      | A finding matched an enabled **Block PR** policy, or a scanner failed while **Fail PR on scan error** is enabled | The status check reports failure. The merge is blocked where the VCS requires the status check |
| **In Progress** | The scan is currently executing                                                                                  | The status check reports a pending state                                                       |

> **Important:** Configure **Cortex AppSec - Code analysis** as a required target-branch check. Otherwise, a **Failed** scan records the violation but does not stop a merge.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/application-security/code-security/application-security-scans-management/manage-scans-through-the-tenant-ui/pull-request-scans/references/reference-d-pr-status-values.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.