Octo.exe promote-release function has unexpected side effects

Hi - we are happily using promote-release to promote releases. We recently noticed some strange behavior.

In our “dev” environemnt we deployed version 1111.01 successfully. Then 1111.02, 1111.03, and 1111.04 failed (everyone was asleep.)

We have a job that runs the promote-release command and it tried to promote 1111.04 ! This clearly failed.

We were wondering if there is a way to tell it to use the LAST SUCESSFUL rather than the current value for promotion.