Lesson 9 / 96 min read
Troubleshooting
Common situations, their causes, and quick fixes.
Symptom → likely cause
| What to do | |
|---|---|
| A generation failed | Retry; if it persists, simplify the prompt or pick another model. A request that never reached the provider releases its reserved credit; usage that started processing counts as spent. |
| "Scope doesn't fit one pass" | Split the scope: build the core, add the rest one by one (or use Autonomous). |
| In-app AI says "try again later" | Out of balance, or the hourly/daily cap is reached. Caps clear on their own as the window passes. |
| Account emails don't arrive | Is the app published and email enabled? On a draft, emails only reach the owner. |
| A campaign is stuck on "sending" | Check your balance: when credit runs out recipients are marked failed. Top up and start a new campaign. |
| The preview differs on mobile | The preview switches to mobile view on phones; compare with the device buttons on desktop. |
The fastest way to report a bug
- 1Copy the exact text
Take the message from the error log verbatim — don't paraphrase.
- 2Write the step
"On this screen, when I press this button" — one sentence is enough.
- 3Hand it to the builder
Paste both together and say "fix this".
Yes. Restore an earlier state from version history with one click; your data is unaffected.
No. Edits go to the draft; visitors keep the previous live version until you republish.
Key takeaways
- Failed generations aren't auto-refunded; only a request that never reached the provider releases its reserved credit.
- Most "not working" cases come down to scope, balance or publish state.
- Error text + the step = the fastest fix.
Related topics
Still stuck? Ask the assistant in the corner, or browse the FAQ.