Troubleshooting

NOME shows the runner but greys out Run. Confirm the machine is awake and the agent is running; for an owner-edge box behind NAT, confirm Tailscale or SSH reachability. Under a service supervisor, check the unit status and logs.

If incremental builds are slow, the warm cache may not be hitting. Confirm the runner is reaching the project-isolated cache store, that cache keys aren't being invalidated by a noisy input (for example a timestamp baked into a layer), and that you aren't forcing a clean build. See BuildKit cache.

A deploy blocked on signature verification means the artifact is unsigned, the signature is broken, or provenance is unverifiable. NOME fails closed here on purpose. Re-run the sign stage and confirm the artifact came from the pipeline that signed it. See Artifact signing.

A blocked deploy means a gate condition isn't satisfied — tests not green, review signals unresolved, artifact not verifiable, branch protection not met, or a missing human approval. NOME reports which condition blocked and never fakes a green. Resolve the named condition and re-run the gate.

If a push or pull/merge request didn't open a run, confirm the connector is still authorized, the webhook signature verified, and the token hasn't been rotated or revoked. NOME fails closed on an unverified payload. Reconnect the connector if the token was rotated. See GitHub and GitLab.

If a CodeRabbit signal isn't showing in the gate, confirm CodeRabbit is installed on the repository and has actually posted a review, and that the same repository is connected to NOME so it can read the status. CodeRabbit is optional — the rest of the pipeline runs whether or not it is connected. See CodeRabbit.