A Repository with 'Enable quiet period' and with 'Maximum retries' set 1 does not put the Build PlanExec to sleep

Issue Summary

A Bamboo Repository with Change detection option setting -Enable quiet period with Maximum retries set 1 does not put the PlanExec to sleep. It builds the build plan immediately after a commit is made to the repository. 

This is working as expected for Maximum retries set > 1

This is reproducible on Data Center: NA

Steps to Reproduce

1. Create a Bitbucket Linked Repository with an Enabled quiet period
   1. Quiet period: 120
   2. Maximum retries: 1
2. Link the repository to a Build Plan
3. Commit something to your repository
4. You will see the build starting in a few seconds after committing a change rather than waiting for 120 secs.

Expected Results

The PlanExec should be sleeping for 120 sec and build the commit.

2023-06-20 11:52:05,196 INFO [10-BAM::PlanExec:pool-12-thread-2] [DefaultChangeDetectionManager] : Found one change for plan 'TES-QUIT', waiting 2 minutes to see if there are any more... (one retry remaining)  

Actual Results

It builds the build plan immediately after a commit is made to the repository. 

The below logs in the atlassian-bamboo.log file:

2023-06-20 11:55:04,609 INFO [http-nio-8827-exec-15] [AuthenticatorImpl] Authenticated app 'Bitbucket:4650619733' as user 'null' successfully
2023-06-20 11:55:05,674 INFO [10-BAM::PlanExec:pool-12-thread-4] [ChangeDetectionListenerAction] : Change detection found 1 change for plan TES-QUIT
2023-06-20 11:55:05,818 INFO [10-BAM::PlanExec:pool-12-thread-4] [ChainExecutionManagerImpl] Build TES-QUIT-JOB1-27 has been dispatched
2023-06-20 11:55:05,820 INFO [AtlassianEvent::0-BAM::EVENTS:pool-1-thread-48] [BuildQueueManagerImpl] Attempting to queue TEST_QUIET_PERIOD - PLAN_Enable_quiet_period - Default Job #27 (TES-QUIT-JOB1-27).
2

Workaround

update the Linked Repository  'Maximum retries: 2'