A request appears unfinished, but its output may still be changing, explicitly stopped, or complete with incorrect behavior. Those states and an exhausted AI allowance need different decisions.
Record the original request, last meaningful output and any actual status before sending another message or closing the app. Preserve active changing output; an animation alone leaves progress unknown, not proven failed after an invented deadline.
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.
Roblox Support tells creators to keep the app open while Build is generating. 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
Creator Hub recommends closing and reopening the app if the continuation request does not work. Apply that step only after a settled unsuccessful continuation, explicit stop or failure, not while output is changing or the response state is unknown. Return to the same project and inspect what is now visible; reopening does not prove a server-side repair, cancellation or deletion.
If you inspect network access or an official app update, record those as editorial diagnostic observations, not universal remedies. Preserve work first and do not reinstall immediately if you have not checked Creations.
Use this order:
- For confirmed stopped unfinished work, send
please continueas a bounded recovery attempt. This guide's recommendation to isolate an attempt is not an official fixed retry limit. - Record acknowledgement or a blocking notice. Preserve changing output and let the current response settle; absence of a final game alone is not failure.
- Only after a settled unsuccessful continuation, use the documented close/reopen step and inspect the same project.
- Check Creations for a matching result; a title or timestamp alone does not establish complete saved output.
- Save the visible error and attempt outcome. Do not keep spending follow-ups to force a clearer diagnosis.
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
For a charged request with missing output, official guidance says to check Creations before contacting Support. Inspect available project identifiers, names and timestamps to locate the intended result, but do not treat listing presence as proof of completion, saving or recovery. Do not interrupt active output for this check.
If a result is located, inspect its actual state before generating the same request again. Use a legitimate test surface only when actually available; do not publish just to perform a private recovery check.
Source check needed for build.playtest. The supporting documentation has not been verified within its review window. Consult the current official sources before relying on this rule.
If the project is present but stopped unfinished, retain the continuation boundary. If it completed with a missing behavior, request a focused repair while preserving working parts. 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. For a charged request that produced no game, Roblox asks for the username, date and time, and any error message. Keep the broader recovery sequence as editorial context.
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. Keep a visible state change separate from proven completed output, and leave unobserved server state unknown.
Choose the observed state
Meaningful output is still changing
Keep the app open and preserve the active request without another recovery message or a close/reopen experiment.
Generation explicitly stopped before finishing
Use the documented continuation instruction without adding a redesign goal. Inspect its send acknowledgement and any usage notice.
The continuation has settled without finishing or explicitly failed
Use the scoped official reopen recommendation, return to the same project and inspect the actual result before another instruction.
A completed result exists but its behavior is wrong
Use the bad-generation repair guide, preserving the working parts rather than restarting the whole concept.
The visible state remains ambiguous
Keep the last meaningful observation and unknown completion status. Do not declare failure from elapsed time or repeated animation alone.
Preserve and compare
The least-destructive action is to retain the original project and request trail, leave active output undisturbed and avoid duplicate generation or spending merely to reproduce a problem.
Hypothetical recovery record: a stopped request receives a continuation acknowledgement; new scene elements then appear. The correct observation is active recovery, even without a final game. If it later explicitly fails, record that new state before applying the reopen guidance. After returning, a similarly named card is only a candidate result until its identity and actual contents are checked. This is an illustrative record, not a performed generation test.
Retest the same request
- Distinguish typed text, acknowledged continuation, blocked send, active output and settled unsuccessful response.
- Match the located creation to the original request and inspect its state; listing presence alone does not establish recovery.
- Record a finished result separately from a behavior mismatch, and leave inaccessible testing untested.
- Stop duplicate requests when the next state remains unexplained; include actual usage or charge observations without making a diagnostic purchase.
Escalate the remaining question
If the documented stopped-work recovery remains unresolved, send official Support the original request context, observed state sequence, acknowledgement or notice, and Creations outcome. For an independently observed charge with missing output, use the dedicated billing/result checklist. Keep passwords, verification documents and payment credentials out of public reports; no recovery or refund result is promised here.