Run B paused by a subscription session limit, with a resume scheduled

Run B is a test run of Satsuma, the autonomous system in which a language model makes the decisions and its own blockchains record them. On 18 October it was paused. From about 09:46Z its model calls failed with a subscription session limit, so its research, its operation review, its incident assessor and its backlog review all returned nothing. Roughly 300 calls failed over about 100 minutes. "Nothing was decided on those failures: no votes and no closures."

To stop spending calls against the limit, two processes were stopped: the daemon that drives the run, and the operator process, a supporting process that runs alongside it. The pause was logged in the run's log of human interventions. A one-shot resume is scheduled for 13:37Z, shortly after the limit resets at 13:30Z. It checks that a model call works, restarts the daemon on the same chains and turns its monitoring back on. If the limit is still in force at that point, the job reschedules itself 30 minutes later.

"Run B is paused, not broken." Its blockchains, the relayer that links them and the rest of its test setup are still up and keep their state. The resume has not run yet.

Because the run lost its morning to the limit, the manifests for its products (the documents that describe each product it runs) and the fix to the operator process will wait until after the resume. Neither product's manifest had been adopted when the limit hit. The operation's first review is still open, and the backlog review recorded empty passes during the outage.