Issue Summary

Builds randomly don't automatically trigger after repository changes after a Bamboo Upgrade

Steps to Reproduce

We were unable to reproduce the issue locally, but the same issue occurred on three different customers.
Customer is coming from 9.6.9 to 10.2.8, but we saw it happening on 10.2.7 and

Expected Results

After a Commit on Bitbucket, it's expected that a Build is triggered on the Bamboo side.

Actual Results

It seems that the lock for the repository, which was used in the previous build, could not be released, so no other builds that need access to this repository could be started
We encounter numerous instances of the following error, which remains unresolved.

2025-10-29 19:42:21,883 DEBUG [AtlassianEvent::1-BAM::EVENTS:pool-2-thread-31] [NonBlockingPlanExecutionServiceImpl] Did not start queue polling job, CHAIN:IN-CC is already being executed
...
2025-10-29 19:42:21,883 DEBUG [AtlassianEvent::1-BAM::EVENTS:pool-2-thread-31] [NonBlockingPlanExecutionServiceImpl] Did not start queue polling job, CHAIN:IN-CC is already being executed
...
2025-10-29 19:42:51,883 DEBUG [AtlassianEvent::1-BAM::EVENTS:pool-2-thread-51] [NonBlockingPlanExecutionServiceImpl] Did not start queue polling job, CHAIN:IN-CC is already being executed

Workaround

It was advised to use -Dbamboo.plan.exe.prioritizing.enabled=false flag, but we were not able to confirm it works, it doesnt seems to completely fix the issue.