One of the features I was excited to gain in the upgrade from 5.x to 6.x was to be able to pause the system, let the running builds complete, and restart for scheduled maintenance with all the queued builds being restored and run. However I'm seeing running builds are never completing because steps don't start after the system is paused. They instead enter the WAITING state. The docs status that it's only The server won't restart because there are builds in the RUNNING state so it's clearly not trying to persist them across the server restart.
Description
One of the features I was excited to gain in the upgrade from 5.x to 6.x was to be able to pause the system, let the running builds complete, and restart for scheduled maintenance with all the queued builds being restored and run. However I'm seeing running builds are never completing because steps don't start after the system is paused. They instead enter the WAITING state. The docs status that it's only The server won't restart because there are builds in the RUNNING state so it's clearly not trying to persist them across the server restart.