Goal runs, Ultracode and the site builder keep going through server updates
Background jobs no longer stop for a server update. They finish their current step, hand over to a new worker that is already running, and continue from there without asking you to confirm anything.
Wer /goal, Ultracode, Agenten oder den Site Builder nutzt: ein Server-Update pausiert sie nicht mehr zur Bestätigung und lässt neue Aufträge nicht warten. Nichts zu tun.
Background jobs run in a separate worker, and every server update replaces it. Until today the old worker had up to five minutes to finish. A step that was still running after that was cut off, and the job paused until you confirmed it. During those minutes no new job started at all.
Text version
When an update starts, the new worker starts next to the old one and takes new jobs at once. The old worker finishes the step it is in, saves its place and hands each job over. The new worker continues at that step. Finished paid steps are not bought again, and nothing waits for your approval.
What changed
A /goal run hands over between two rounds, Ultracode between two calls, an agent between two steps and the site builder at the start of its next build stage. A step that is already running always finishes first, so nothing runs twice.
The new worker no longer waits until the old one has finished. It starts in the same service, takes over as soon as it is ready, and the old one finishes in the background.
Pressing Stop still wins: a job you stopped stays stopped.
Prices and plans did not change.