A GitHub action did not take effect
An issue was not picked up
An issue was not picked up
Check that the Factory is enabled and the open issue is on the bound board, out of Triage, and
not held. Ordinary pickup needs all pickup labels. A configured fast-lane label trigger uses its
own label instead; the Factory still checks who applied it before using it to approve a plan. A GitHub Project owned by a personal account can’t be bound to a Cloud
Factory. Use an organization-owned Project instead. A queue can also mean that active-run capacity
is full.
A label, review or comment was ignored
A label, review or comment was ignored
Check the gate, the run’s pinned label names, and who may approve.
Board events supply pickup, gate labels and item comments; the PR review event comes through the
GitHub App and does not depend on a card move. A boardless PR may not have a board label or comment
route. A plain PR comment doesn’t approve or request changes.Check whether a new GitHub event was delivered. If the gate is still pending, use the exact
architech factory runs approve command shown in the Inbox to avoid relying on GitHub delivery.
GATE_NOT_PENDING means the specified gate isn’t waiting. Inspect the run again; the default
pipeline does not wait for a check gate.An approved PR hasn't merged
An approved PR hasn't merged
Check for holds on the PR, parent issue and sub-item. Then check the merge preset, current head,
CI and whether GitHub reports a conflict. PR approval and merge authority
are separate. A newer push invalidates review evidence for the previous head.
A stage is waiting or quiet
Retry, skip or roll back
Read the stopped stage’s question and pick an offered action, not a generic retry:- Retry the stage retries the stopped work. Cancel the run ends the run.
- Skip this sub-item, when offered, closes that part without a PR and lets the rest proceed.
- Resume the session, when offered for a provider stoppage, continues the same session.
- Roll back, when offered, restores the last complete checkpoint. Work after it is lost.
Recover work the App could not push
Read the escalation before using its download or Git instructions. A valid checksum and a successfulgit bundle verify do not tell you whether a bundle contains publishable source.
Committed-work recovery
Use this path only when the escalation explicitly gives a source commit to publish and its destination branch. If it says the commit is already on the remote, don’t publish it again. If the remote state could not be checked, check the named branch first. In your clone, follow the escalation’s download command. Compare the bundle’s SHA-256 checksum with the value in the escalation and rungit bundle verify as instructed. Stop if the checksum
is different or verification fails. Then use the escalation’s fetch command for the exact
source commit SHA it names.
Only after the fetch succeeds, check that origin points to the correct repository and that the
source SHA and destination branch match the escalation. Use the exact push command from the escalation
with your authorized account; do not force-push.