Reference E: 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.