> 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-c-scan-health-values.md).

# Reference C: Scan health values

Scan health indicates whether all scanners completed execution during a scan. It applies to pull request scans, CI scans, and branch periodic scans.

| Scan health     | Meaning for a pull request scan                                    | Enforcement consequence                                                                                           | Next action                                                                                                 |
| --------------- | ------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------- |
| **Completed**   | Every enabled scanner completed execution against the diff         | The PR status reflects a complete evaluation of the change                                                        | Act on the PR status                                                                                        |
| **Partially**   | One or more scanners failed or were skipped while others succeeded | The PR status was determined on partial evidence. A **Passed** result does not establish that the change is clean | Treat the merge as ungoverned. Diagnose integration health, and consider enabling **Fail PR on scan error** |
| **Error**       | The scan failed to complete                                        | No evaluation occurred. The merge proceeds unless **Fail PR on scan error** is enabled                            | Diagnose the cause in the data source instance health view                                                  |
| **In Progress** | The scan is currently executing                                    | The status check reports a pending state in the VCS                                                               | Wait for completion. No rescan action exists                                                                |

> **Note:** Pull request scans offer no **Rescan** action. Re-evaluation occurs when a new commit is pushed to the pull request.


---

# 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-c-scan-health-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.