Build stuck in the queue due to "Waiting for pending UI settings changes to complete" after changing project settings when Versioned Settings are enabled and the VCS branch is protected

Affected versions: 2025.11.4

Problem

1. Versioned Settings are enabled.
2. VCS branch is protected (push without a pull request is prohibited).
3. Changing project settings via UI and starting a build results in the build getting stuck in the queue due to Waiting for pending UI settings changes to complete.

Cause

Changing project settings via the web UI when Versioned Settings are enabled causes TeamCity to attempt to push new settings to the Versioned Settings repository. Branch protection prevents pushes, and TeamCity can never commit the new settings.

Resolution

Quick Fix

1. Disable Versioned Settings.
2. Re-enable Versioned Settings.
3. When TeamCity prompts whether it should "Overwrite settings in the VCS" or "Import settings from VCS", choose the latter. WARNING: This will discard the current project settings on the server and replace them with the settings stored in the VCS.

Longer-Term Solution

• Option A: Allow TeamCity to bypass the branch protection rules. Depending on how TeamCity authenticates in the VCS, this may require reconfiguring the VCS root used for Versioned Settings.
• Option B: Disable editing project settings via the web UI: project settings > Versioned Settings > untick "Allow editing project settings via UI". That would prevent TeamCity from trying to push to the settings repo. In this case, when project settings need to be updated, they should be updated by editing the DSL code in the IDE and submitting a PR.

More information

For protected branch support by Versioned Settings, upvote this feature request: https://youtrack.jetbrains.com/issue/TW-57533.