Octopus UI references previous version control settings when they are updated via an external method

[dan-close]

Severity

1 customer reported

Version

2026.2.13158

Latest Version

I could reproduce the problem in the latest build

What happened?

When changing the version control settings for a project with an external tool (such as the Octopus Terraform provider), the Octopus UI attempts to load the project using the previous settings. Ideally, we should validate the version control settings in the browser cache and update them if necessary.

Reproduction

1. Have a version-controlled project pointing at Git repo A with default branch master (OCL files present in .octopus/ on master).
2. Browse the project in the UI (so the browser stores the selected branch).
3. Update the project's version control settings (in our case via the Terraform provider) to point at Git repo B with the default branch develop. Repo B contains valid OCL files (schema_version.ocl etc.) in .octopus/ on develop, and has no .octopus directory on master.
4. Reload the project in the same browser session.

Error and Stacktrace

Octopus configuration not found in the ".octopus/<folder name>" directory of reference refs/heads/master: The file 'schema_version.ocl' does not exist in the Git repository.

More Information

Workaround

Clearing the browser cache will force an update to the 'localStorage' and pick up the new version control settings.