> 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/ci-scans/references/reference-c-scan-health-values.md).

# Reference C: Scan health values

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

| Scan health             | Meaning for a CI scan                                          | Enforcement consequence                                                                               | Next action                                                                                                                                                                                                                   |
| ----------------------- | -------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Completed**           | Every enabled scanner completed execution.                     | The CI status reflects a complete evaluation.                                                         | Act on the CI status.                                                                                                                                                                                                         |
| **Partially Completed** | One or more scanners failed or were skipped. Others succeeded. | The build outcome used partial evidence. A **Passed** result does not establish a clean artifact.     | Re-run the pipeline after correcting the cause. For a shipped artifact, evaluate the branch against the latest branch periodic scan. Treat that result as the substitute assessment until the pipeline reports **Completed**. |
| **Error**               | The scan failed to complete.                                   | No evaluation occurred. The pipeline outcome depends on the CLI exit code and pipeline configuration. | Diagnose the pipeline log. Exit code `2` indicates an internal, network, or authentication error.                                                                                                                             |
| **In Progress**         | The scan is executing.                                         | The result is not final.                                                                              | Wait for completion. CI scans have no rescan action.                                                                                                                                                                          |

{% hint style="info" %}
Unlike a branch periodic scan, a CI scan has no **Rescan** action. Re-evaluate by running the pipeline again.
{% endhint %}


---

# 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/ci-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.