ArgoCD deployments on Octopus Server update the ArgoApp, but Octopus reports a Git Drift error in Live Status and times out waiting for the sync to complete.

[Clare-Octopus]

Severity

Not blocking customers, Argo App does Sync changes correctly but Octopus deployment fails - leading to customer confusion.

Version

2026.2.13126

Latest Version

None

What happened?

This is specific to Octopus Server, testing on Octopus Cloud versions worked fine for me.

If I use either of the Octopus Argo steps - Update Argo CD Application Manifests or Update Argo CD Application Image Tags the deployment will update the Argo application itself and will sync that update. But Octopus won't register the sync. You will see a Git Drift issue in the Live Status and the deployment will eventually timeout on the step where it waits for the application to sync.

I am using the same gateway and helm chart versions between Octopus Cloud and Octopus Server, and deployments work fine on Octopus Cloud, so this doesn't seem to be a chart/gateway version issue. It seems to be an issue specifically with the Octopus version being used.

I can confirm my ArgoCD Gateway on Octopus Server health checks fine and it did update with a later chart version.

Octopus Cloud 2026.3.1737:

Octopus Server 2026.2.13126:

Octopus Server Chart versions (the same as Octopus Cloud):

Octopus Server K8s Live Status:

Reproduction

1. Have an ArgoCD instance setup with the ArgoCD gateway installed and some Argo Apps.
2. Create an Octopus project with either a Update Argo CD Application Manifests or Update Argo CD Application Image Tags step in it.
3. Connect an Argo app to the project using Argo/Octopus Annotations on the Argo App.
4. Setup the rest of the step and deploy it.
5. See it update the Argo app with the configured changes but then see the Git Drift in the Live status for that app in Octopus and see the deployment fail with the Wait for Argo CD Applications for 'Update Argo CD Application Image Tags' action timing out.

Error and Stacktrace

13:41:19   Info     |       Pausing the deployment while waiting for Argo CD applications to become healthy
13:41:20   Info     |       Wait for Argo CD Applications for 'Update Argo CD Application Image Tags' is still waiting for status to be in sync and healthy for ArgoCD applications
                    |       Waiting for Argo CD application Git revision to refresh: [OctoArgoServer/helm-myapp-server-dev[0]]
                    |       Waiting for Argo CD application to sync: []
                    |       Waiting for Argo CD application to become healthy: []
                    |       Waiting for Argo CD application to stabilize: []
13:41:51   Info     |       Wait for Argo CD Applications for 'Update Argo CD Application Image Tags' is still waiting for status to be in sync and healthy for ArgoCD applications

More Information

Initial customer ticket (internal) - https://octopuscd.zendesk.com/agent/tickets/209561
RnD Thread (Internal) - https://octopusdeploy.slack.com/archives/CNHBHV2BX/p1781616513557509

Workaround

None at the moment, the changes will be applied to your ArgoApplication but Octopus will fail the deployment so at present you may have to rely on manually checking your Git repos to ensure they have been updated and/ or manually checking the Argo App in Argo itself to ensure the changes have been made.

[philipkotliyakov]

Release Note: Fixed an issue where the 'Update Argo CD Application Manifests' step with Git Commit Method set to
Direct Commit did not record the deployed commit in Octopus, causing the application's tracked commit to never
advance and the 'Wait for Argo CD Applications' step to either pass without verification or time out with Git Drift.

[team-builds-bot]

🎉 The fix for this issue has been released in:

Release stream	Release
2026.2	2026.2.13147
2026.3	tbc