> 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/branch-periodic-scans/references/reference-d-instance-health-error-types.md).

# Reference D: Instance health error types

The data source instance health view classifies each error by type. Use the error type to determine the correction required before a rescan can succeed.

| Error type               | Meaning                                                                                                                                           | Effect on periodic scanning                                                                                            | Correction                                                                                                                                                                                                                                                                                      |
| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Token**                | The access token for the integration is invalid, expired, or revoked.                                                                             | The scan cannot authenticate to the VCS provider. Scan health reports **Error**.                                       | Rotate or reauthorize the integration credential from **Settings** > **Data Sources & Integrations**. A rescan before the credential is restored repeats the failure.                                                                                                                           |
| **Permission**           | The integration lacks a permission required for the operation. Missing permissions are classified as an error or a warning according to severity. | Scanning fails, or a specific capability is unavailable, according to which permission is missing.                     | Grant the missing permission on the VCS provider. Read the description on the repository-level health entry to identify the specific permission. For the required permission set, see GitHub SaaS onboarding or Azure DevOps SaaS onboarding; for other providers, see Onboarding data sources. |
| **Clone**                | The repository contents could not be retrieved.                                                                                                   | The scan has no code to analyze. Scan health reports **Error**.                                                        | Verify that the repository is accessible and not archived, and that the integration retains read access to the repository contents.                                                                                                                                                             |
| **Connection**           | Cortex Cloud could not reach the VCS provider instance.                                                                                           | Scans fail for the affected instance until connectivity is restored.                                                   | Verify network reachability and the availability of the provider instance, including any firewall or allow list restriction on a self-hosted instance.                                                                                                                                          |
| **Webhook subscription** | The webhook subscription for the instance failed. Webhook subscription errors are classified as an error or a warning according to severity.      | Event-triggered scanning, including pull request scanning, does not fire. Periodic scanning continues on the schedule. | Reestablish the webhook subscription for the instance.                                                                                                                                                                                                                                          |


---

# 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/branch-periodic-scans/references/reference-d-instance-health-error-types.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.