Docs - Troubleshooting and checklists
Failed or stuck build
Recover when work stops, fails, or keeps waiting.
A failed or stuck build needs a calm diagnostic pass. The visible status usually tells you whether the issue is credits, preview readiness, repair, external setup, or a retryable build problem.
How to use this
- 1Read the status message before starting a new prompt.
- 2Check whether credits, trust gates, or external setup are blocking work.
- 3Ask for repair with the exact visible issue.
- 4Contact support if the same problem repeats after repair.
Keep in mind
- Starting many new runs can make troubleshooting harder.
- External integrations may need manual setup before repair can succeed.
- Keep the next prompt narrow while recovering.
failed website buildstuck AI buildDriftLess troubleshooting
Last reviewed: 2026-06-01