Check Git Sync status and resolve upload failures

Check Git Sync in Version History to see whether a Flow or Subflow version has uploaded to the mapped Git repository.

Check a version’s sync status

Open the Flow or Subflow.
Open Version History.
Review the Git Sync column.

Status	Meaning	What to do
Success	The version uploaded to the mapped repository.	No action is needed.
Error	The upload failed. Hover over the status to view the error.	Resolve the cause, then select Sync when available.
Warning	The version may be queued, processing, waiting for retry, or blocked by an earlier failure.	Wait if processing. If the warning remains, check for an earlier failed upload or ask an administrator to review the queue.
Deprecated	The version has no upload queue entry.	Contact an administrator if the version should be available from Git.

Resolve an upload failure

A failed upload does not delete the saved Leapwork version. Later versions of the same Flow or Subflow wait until the failed upload succeeds. Other assets can continue to synchronize.

Review the error shown when you hover over Error.
Check that the Controller can reach the Git provider over HTTPS.
Check that the Git connection, repository mapping, and required PATs are correct and current.
Check that the token identity has repository write access.
Resolve any provider approval or security block.
Select Sync from the Flows pane notification when available.
Refresh Version History and confirm that the status changes to Success.

A retry is available only for a failed queue item and requires the user to have the necessary edit permission.

Check migration status

Status	Meaning	Next step
Not Applicable	The team has no existing Flow or Subflow history to migrate.	Enable the mapping without migration.
Not Started	Existing history has not been migrated.	Run migration before enabling the mapping.
Migrating	Versions are transferring to the repository.	Wait. Do not create, save, import, or edit the team’s Flows or Subflows, and do not run preview runs.
Completed	The selected versions transferred successfully.	Verify a test save and its Git Sync status.
Partial	Some selected versions transferred and others did not.	Resolve the reported issue and retry where available.
Failed	Migration did not complete.	Resolve the reported issue and retry where available.

If the issue continues

Check the Controller’s connection to the provider, the selected Git provider and repository, PAT validity and permissions, and whether the repository’s branch rules allow Leapwork to write. For migration issues, also confirm that you are in the mapped team.