Error & status codes

Reference for the user-visible error and status codes emitted by Pipemason, with what each one means and how to recover.

rate_limited

Means: the cloud control plane is rate-limiting your requests (roughly 60–120 req/min depending on the route). Recover: wait a moment and retry. In normal use you should not hit this — if it persists, email support@pipemason.com. If you are load-testing, contact support first.

run_quota_exceeded

Means: you reached the Free-tier cap of 10 runs per calendar month. Recover: upgrade your plan, or wait for the quota to reset at the start of the next calendar month.

repo_quota_exceeded

Means: you tried to use more repositories than your plan allows (Free: 1 repo; Solo: 5 repos; Team and Enterprise: unlimited). Recover: upgrade your plan, or disconnect a repo to free a slot.

GitHub token expired / revoked

Means: the GitHub OAuth token the cloud holds for you is no longer valid — usually because it was revoked. Recover: go to pipemason.com/settings, click Disconnect, then Connect GitHub again to re-authorize the repo + read:user scopes.

escalation

Means: the monitor hit something it cannot safely resolve on its own — a gate failure it could not recover from, a contract disagreement between domains, or another ambiguous decision — so the run is paused awaiting you rather than guessing. Recover: open .pipeline/STATE.md; the escalation block states exactly what is needed. Fix the underlying issue, then run:

pipemason resume

rebase_conflict

Means: a git rebase produced conflicts. Pipemason never auto-resolves rebase conflicts — it escalates and pauses the run awaiting you. Recover: resolve the conflicts in your working tree as you normally would, then resume:

pipemason resume

Getting help

For step-by-step recovery, see Troubleshooting. For anything not covered here, email support@pipemason.com with your Clerk user id so we can locate your run.