Recover or cancel an Agent run

Quadratique makes execution failures and lost leases visible. It does not silently run the same issue again, because an automatic duplicate could produce conflicting code or pull requests.

A run remains queued

Check the following:

• the bound machine is online;
• the configured Runtime and model are still available;
• the Agent and machine are shared when another member initiated routing;
• the board is in the Agent allowlist; and
• the machine has a free execution slot.

The default concurrency cap is 2. A third issue remains queued until capacity is available. Lowering the cap does not kill active work; the machine drains before accepting another run.

Start acknowledgement expires

A claimed run must acknowledge its start within 30 seconds. If it does not, the claim expires and the issue does not move to In Progress.

A running machine disconnects

The daemon renews a 60-second run lease every 20 seconds. If renewal stops and the lease expires, Quadratique marks the run Interrupted.

Inspect the machine and transcript, then manually redispatch when it is safe. Quadratique does not launch a replacement automatically.

Cancel a run

Request cancellation from the issue’s run controls. Cancellation remains pending until the daemon acknowledges that execution stopped or the lease expires.

After acknowledgement, the issue returns to To Do and keeps its Agent routing. You can clear the routing, select another authorized Agent, or dispatch again.

Runtime or model is unavailable

Quadratique fails closed. It reports the unavailable Runtime or model, keeps the issue in To Do, and does not substitute another model or machine configuration. Rebind the Agent to an available Runtime or restore the original one before redispatching.

A machine is removed

Removing a machine revokes its credential, suspends bound Agents, and clears their queued routing. Rebind or replace the suspended Agents before delegating those issues again.

Work is rejected in Human Review

Provide actionable feedback when rejecting. The next run uses the current Agent revision and the feedback, rather than mutating or resuming the reviewed run.