Generation is slow or stuck

What's normal#

• A single screen — usually under a minute.
• A multi-screen flow — screens are designed one at a time, so a five-screen flow takes roughly five times a single screen.
• A website clone — noticeably longer, because a real browser loads the target page before any design work begins.
• A whole-project code export — runs as a background job; larger projects take longer.

If screens are appearing on the canvas one after another, it's working. Let it run.

What's not normal#

• No progress at all for several minutes.
• The chat stops mid-turn with no message and no error.
• A background job that never reports completion.

What to do#

1. Reload the page. The run continues server-side; you're just reconnecting to it.
2. Check the canvas. Screens completed before the stall are there.
3. Ask for what's missing, rather than restarting the whole request — that avoids paying twice for work already done.
4. If it's reproducible, contact support with the project link and the time.

Making runs faster#

• Smaller batches. Three screens then three more beats ten in one go, and you can course-correct in between.
• Targeted edits over regeneration — faster as well as cheaper.
• Settle the theme first, so you're not rebuilding screens to fix colour.