Landing freezes end by themselves

What a landing freeze is

Auto-landing can be switched off on purpose — for a rebuild, a hand merge, or a procedure that needs master to hold still. That off-switch is the auto-lander supervisor switch, and it stops every landing at once.

A freeze used to be a plain flag: once set, it stayed set until somebody remembered to clear it. On 1 November 2026 a session froze landing at 1:44 AM and then ended, and nothing ended the freeze with it — so 26 finished branches sat unlanded for about seven hours, until the freeze was lifted by hand.

A freeze is now a lease. It always carries two things:

• who set it — the session that froze landing, or the person at the terminal;
• when it ends.

What that means for you

• It ends by itself. At its end time the freeze simply stops holding, and the branches land on the next pass. You do not have to switch anything back on.
• It ends if the session that set it ends. An agent that freezes landing and then finishes, crashes or is archived does not leave landing off behind it.
• It cannot be set without both halves. A freeze that names no setter or no end time is refused when it is set, and ignored if it was written by hand.
• It cannot exceed an hour. A freeze is for a procedure, not for keeping landing off indefinitely. If you want landing off for good, that is the auto-landing setting, not a freeze.

When a freeze keeps holding

If a freeze is still holding after 30 minutes, Omniscio raises one card in your inbox. It tells you:

• who set it and why (in the words they gave);
• how long it has been holding;
• how long it has left;
• and it carries a Lift the freeze button that clears it immediately.

You get that card once per freeze, not once per tick, and it clears itself as soon as the freeze is gone.

For scripts and agents

Setting a freeze from the command line takes an end time and a reason:

npm run lander:switch -- set auto-lander-supervisor --for 30 --reason "rebuilding the app"

--for is in minutes, up to 60. Without it the freeze lasts two minutes; --no-expiry takes the one-hour cap instead (the Integration Engine handover uses it). An --until instant works too, and must be no more than an hour away. clear lifts it early.

npm run lander:switch -- list prints, under a frozen switch, who set it, why, and how long is left.

Related

• Auto-lander dashboard — watch and pause the lander from the panel.
• Inbox alerts — where the freeze card arrives.