An entity in Cortex might be unexpectedly archived for several reasons, most commonly related to auto-archiving settings and integration issues:
- Auto-Archiving Settings: If auto-archiving is enabled, Cortex will archive entities when they are no longer detected in the source system (such as a Git repository, cloud provider, or other integration). For example, if a service’s YAML file is deleted from the repo (GitOps-based) or if the backing repository is archived or becomes inaccessible (integration-based), the entity will be archived in Cortex. If both GitOps-based and integration-based auto-archiving are enabled, integration-based logic takes precedence and can override manual or GitOps-based changes.
- Integration or Token Issues: If the integration with a source system (e.g., GitHub, Azure, GCP) is misconfigured, has expired tokens, or loses access (such as a deleted admin user or missing org membership), Cortex may not be able to detect the entity and will archive it during the next sync. Once the integration is restored, entities may be unarchived automatically.
- Repository or File Name Mismatch: If the repository name in the catalog descriptor does not exactly match (including case sensitivity) the actual repository name, Cortex may not detect the entity and will archive it. Commonly, when users have multiple git configurations, they may forget to add the appropriate alias. If so, we will look at the default configuration and the repository may not detected, which can result in auto archival
If you notice unexpected archiving, it’s recommended to review your auto-archiving settings, check integration health and permissions, or consult audit logs for recent changes. If the cause remains unclear, feel free to reach out to Cortex support.