Troubleshooting playbook
Anyone unblocking a failed deploy, key bind, branch map, or access issue.
Structured checklists for the failures teams hit most often: keys, plan caps, branch refs, install progress, email, and access confusion.
Work top to bottom within each section. Most incidents are mis-bound keys, exhausted plan capacity, or GitHub refs that moved — confirm those before deeper infrastructure debugging.
5 sections4 key takeaways3 related guides
Quick highlights
Work top to bottom within each section. Most incidents are mis-bound keys, exhausted plan capacity, or GitHub refs that moved — confirm those before deeper infrastructure debugging.
Each numbered section maps to a support category. Gather project slug, environment, exact error text, and recent build ID before escalating.
What you will learn
- Start with subscription and plan validation — many 403/409 errors originate here.
- Branch/ref issues usually mean mapping drift or missing GitHub branches.
- Install/deploy stalls often clear after webhook or mapping fixes plus one controlled rebuild.
- Missing email rarely blocks product behavior — fix SMTP in parallel with user comms.
Sections in this guide