Issue: Some changes made via GitOps didn't reflect in Cortex due to UI editing being enabled. A full reprocess is needed now that GitOps once UI editing has been disabled.
Explanation:
In GitOps, entities are managed through descriptor files and synced from your Git repo. If UI editing is enabled, Git-based changes are ignored. If you discover that UI editing was turned on at any point when using GitOps, you'll need to trigger a full reprocess so Cortex reflects the state of your Git repo.
Solution:
Ensure UI editing is disabled for Entities
Go to Settings > GitOps > Entities and make sure UI editing is toggled OFF.Enable Cortex YAML processing setting:
Verify that the Cortex YAML processing setting is enabled in the admin settings at https://app.getcortexapp.com/admin/settings/gitops. Without this setting enabled, configuration changes in your repository won't be processed by Cortex.Toggle the Scorecard UI Editor setting:
Go to Settings > Gitops > Scorecards. Note the Enable GitOps for Scorecard editing toggle: Toggle it OFF, then ON, and then back OFF again.Make an empty commit:
Push an empty commit to your Git provider (e.g., GitHub, GitLab) in a repository that Cortex has access to.
Additional Troubleshooting:
Verify the file path of your catalog YAML is correct
Ensure Cortex has proper access to the repository
Check for any GitHub API errors or access issues
Check the GitOps logs for specific error messages, particularly YAML validation errors
Related Resources: