Documentation · Help
Troubleshooting
The platform's failure philosophy: stop, surface the reason where you'll see it, and never retry silently. Most "something's wrong" moments are one of these.
Tickets
| Symptom | What it means / what to do |
|---|
| Ticket bounced back to To Do with a red note | The note is the exact reason. Most common: a required document is awaiting approval (re-approve it under Documents), or the run failed terminally (read the last-attempt error, fix the cause or just re-dispatch). |
| "Generate details first" when starting a ticket | By design — open the ticket, click Generate details, review, then implement. |
| Ticket stuck In Progress with no logs | Check the build VM is online (Settings → Execution Targets). If it went offline mid-run, bring it back; the run fails over with a reason rather than hanging forever. |
Auto-deliver
| Symptom | What it means / what to do |
|---|
| Paused with "Milestone … delivered — PR open" | Working as designed: review and merge the milestone PR, then go Approve it. |
| Approve button greyed out | Working as designed: it only lights up once every ticket in the milestone shows Done. |
| Popup says to merge the pull request first | Working as designed: you clicked Approve before merging the milestone's PR. Merge it on GitHub (the popup links straight to it), then click Approve again. |
| Approve button shows "Reviewing…" for several minutes | Working as designed: an automated technical-debt review session is checking the merged PR against the milestone's scope and general code health. It reports back on its own — no need to click anything while it runs. |
| Approve found new tickets instead of approving | Working as designed: the technical-debt review found something worth fixing and filed it as a real ticket on the same milestone rather than approving over it. Auto-deliver works through those tickets automatically; once they're Done, click Approve again. |
| Paused with a ticket failure reason | The loop never runs past a broken state. Fix or re-dispatch the named ticket manually, then Resume. |
| Paused with "E2E pass failed after repairs" | The integrated stack has a bug automation couldn't converge on. The milestone branch holds everything — inspect the E2E output, fix (or file a ticket for the fix), then Resume. |
Documents
| Symptom | What it means / what to do |
|---|
| Buttons disabled, "AI is refining…" banner | A rewrite is running server-side. Safe to navigate away; the page updates when it finishes. Entries older than 15 minutes are treated as stale automatically. |
| A previously approved document shows draft | Someone edited/refined/regenerated it — approval always refers to exact content. Re-review and approve; ticket dispatching resumes. |
| Made it worse with a refine | Open History and restore any earlier version. |
AI & billing
| Symptom | What it means / what to do |
|---|
| "Monthly budget reached" / "Prepaid balance exhausted" | Your own guardrails firing. Raise the budget or top up in Admin. |
| "No online build VM with Claude Code available" | Dev-mode subscription routing can't find a capable VM — see the checklist in the subscription guide. |
| Calls slow or failing after heavy subscription use | Subscription rate limits. If a fallback model is routed, work continues automatically; otherwise wait for the window to reset. |
