Skip to content

Rescue stuck work

Rescue needs the graph engine.

  1. Turn it on in ~/.cambium/config.json:

    {
    "engine": "graph",
    "phases": { "rescue": { "cap": 1 } },
    "rescue": { "causeRepo": "owner/tooling" }
    }

    causeRepo is where root-cause tickets go; leave it null to file them in the stuck item’s own repository.

  2. Restart if you changed engine: oakgreen restart cambium.

Every hour (rescue.everyMinutes) cambium looks for stuck items, starts a read-only diagnosis worker for each, carries out its plan, files root-cause tickets labelled q:intake and rescue, and leaves a report comment on the item.

See what is stuck, without changing anything

Section titled “See what is stuck, without changing anything”
Terminal window
cambium run rescue --repo owner/name
Terminal window
cambium run rescue --repo owner/name --issue 42
Key under rescue Default Controls
staleHours 12 how long an issue or PR may sit before it counts as stuck
graceMinutes 30 how long after a label change before it counts
cooldownHours 24 gap between rescues of one item
maxRescues 2 rescues in a week before it goes to q:human with why:rescue

Symptoms and actions in full: cambium graphs.