A stopped generation and an exhausted AI allowance are different states. Use the documented recovery message first, then verify whether the project already exists before starting over.

First recovery step: type “please continue”

Roblox Creator Hub says that if Build stops before the game is finished, send the exact follow-up message please continue. Keep it short. Adding new mechanics to the recovery message makes it harder to tell whether Build resumed the interrupted work or began a different revision.

Wait for the active response to settle before sending another message. Repeated taps or duplicate prompts can create overlapping instructions and use more allowance without clarifying the state.

If “please continue” does not work

Close and reopen the Roblox app, return to Build, and check the project. This refreshes the visible app state without assuming that the server-side generation disappeared. Confirm network access and app updates, but do not reinstall immediately if you have not checked Creations.

Use this order:

  1. Send please continue once.
  2. Let the current response finish or fail.
  3. Fully close and reopen the app.
  4. Open Creations and look for the project.
  5. Save the visible error before trying a new concept.

The first-game workflow explains the normal sequence. If the generated game exists but behaves incorrectly, use the bad-generation repair guide; that is not a stuck generation.

Stopped generation versus AI usage limit

Each Build message consumes part of the daily AI allowance. Creator Hub calls each message one prompt, including follow-up changes. However, Roblox says that if allowance runs out during an active generation, that generation should finish. The next message can require free usage after reset or purchased credits.

Do not diagnose every pause as an allowance problem. Check the in-app usage display, then read the AI usage guide for what counts and what Roblox has not published about reset timing.

Check Creations before restarting

A generation can finish after the visible chat looks stalled. Open Creations and compare project names and timestamps. If a result is there, playtest it rather than generating the same request again. Starting from scratch too early can produce duplicates and makes a payment dispute harder to describe.

If the project is present but incomplete, resume from its chat and request one missing behavior. If no project appears and Robux was charged, move to the charged Robux but no game checklist.

Save evidence for Support

Before contacting Roblox Support, record the account username, approximate date and time with timezone, project or prompt summary, visible error message, whether please continue was tried, whether the app was reopened, and whether Creations was checked. Do not send passwords, age-check documents or payment credentials.

These details do not guarantee an outcome, but they give Support the identifiers Roblox asks for and preserve the sequence while it is fresh.

Keep the recovery test controlled

Use the same project and one recovery action at a time. Note whether chat resumed, whether a new creation appeared and whether the usage display changed. If you switch networks or update the app, record that transition rather than doing several changes together. A controlled sequence helps distinguish a display refresh from a completed server-side generation and keeps a later Support report understandable.