Troubleshooting

Troubleshooting Git integration issues

You might encounter the following:

Unexpected loss of assets

Assets can be deleted and unsaved changes can be lost:
  • When one user accidentally checks out a project space or project that another user modified in a different branch.
  • When a user does a Git pull or a discard before committing changes.

You can restore deleted assets from the Recycle Bin, but they won't contain uncommitted changes.

Branch or tag lists are empty, or checkout fails

SnapLogic requests Contents: Read & write permission on the connected GitHub App to list branches and tags. If that permission is missing or was not approved, branch and tag lookups return an empty list even though the request succeeds, and checkout can fail.

In GitHub, verify that the connected GitHub App has Contents: Read & write permission on the target repositories, and confirm that a GitHub organization administrator has approved that permission request. Refer to Configure GitHub or GitHub Enterprise Cloud for the install and approval steps, or, for *.ghe.com organizations, Configure GitHub Enterprise Cloud with data residency.

Commit, checkout, or pull fails with a file limit error

The project exceeds a Git Integration file limit. The operation fails with one of these errors:
  • File is too large for Git integration: <file name> (<size> > 52428800)
  • Too many files (including hidden git objects) in project to commit to Git: <project> (<count> is larger than 1000)
  • Too many files in repository to be used with Git integration: <project> (<count> is larger than 1000)

Redistribute the project's contents across enough projects to bring each one under the limit. Count every file in the project's folder, not just the tracked assets, and remember that a project holding more than 2,000 files needs more than one additional project. For a file that exceeds 50 MB, remove it from the project or stop tracking it.

An asset shows a stale reference after checkout

After a Git checkout, the UI can still display the asset's previous reference.

Delete the asset, then do a hard reset in Git and confirm that the asset resolves correctly.

Pipeline status is Modified after checkout

The pipeline references accounts or Snaplexes that do not exist in the destination environment. During checkout, those references are removed and the pipeline is marked as Modified. This is expected behavior.

Open the pipeline in Designer and reconfigure the missing account and Snaplex references using resources available in the destination environment.