Git and data model deployment troubleshooting
Zenlytic data model changes may use Git behind the scenes so teams can review, version, and deploy changes safely.
If a data model change is not showing up, the issue is usually related to one of these:
The change was saved but not deployed
The workspace is looking at a different branch
Git credentials or deploy keys are not configured correctly
There is a merge conflict
The change was made in the wrong workspace or environment
Check whether the change was deployed
After editing the data model, confirm the change has been deployed to the environment users are querying.
If the change is only saved on a development branch, users may not see it in production yet.
Check the branch
Confirm the workspace is looking at the branch you expect.
If the workspace is on a development branch, results may differ from production. If the workspace is on production, undeployed development changes will not appear yet.
Check Git access
If Zenlytic cannot save or deploy changes, check the Git connection and credentials for the workspace.
For customer-managed Git repositories, confirm that the deploy key or token has the required access.
Merge conflicts
A merge conflict can happen when two sets of changes edit the same file or incompatible parts of the data model.
If you see a merge conflict:
Do not keep making changes on top of the conflict.
Review which files are affected.
Decide which version of the change should win.
Resolve the conflict in Git or with help from your data model owner.
Deploy again after the conflict is resolved.
When to contact support
Contact support if:
You cannot save or deploy data model changes
The Git connection appears broken
You are unsure which branch is live
A merge conflict blocks deployment
A deployed change does not appear in Zoë or Explore
Include the workspace name, branch name, affected file or model, the error message, and what changed recently.