BC-0157 · TROUBLESHOOTING
Editorial review 2026-09-26
Roblox Build Generation Paused
Before treating generation as paused, identify whether output is still changing, an explicit stopped state is shown, or the game has finished but behaves incorrectly. Use the documented continuation path for stopped unfinished work; do not infer a pause from an invented time limit.
Symptom
Generation appears paused or stopped before a clearly completed game result.
Immediate action
Classify the current output and completion evidence before sending a recovery request.
Diagnostic branches
- Meaningful generated output is still changing.
- Preserve the active request and avoid introducing overlapping instructions.
- The interface shows stopped unfinished work.
- Use the documented continuation path within the available usage workflow.
- A completed playable result exists but a behavior is wrong.
- Use the behavior-specific repair guide instead of describing an unfinished generation.
- No clear stopped or completed state can be established.
- Record the ambiguity and last change without assigning a fabricated timeout.
Least-destructive change
Keep the current request and output intact, using a scoped recovery only for the state it addresses.
Retest
- The state record distinguishes changing output from an animation alone.
- A missing gameplay behavior is not automatically called incomplete generation.
- The recovery message does not introduce another design objective.
Escalation
If the stopped state remains after the documented recovery path, use the failed-continuation record with the original request and observed response. No hidden pause control or maximum generation duration is asserted.
Working notes
Keep the active request and last visible output together. Record any status wording and the most recent meaningful change. A spinner alone and newly generated content are different evidence; neither should be converted into a precise backend state the interface does not show.
If the game has reached a playable result with a missing behavior, distinguish a completed poor result from an unfinished generation. That difference changes the next instruction: a bounded behavior correction is not the same request as continuing interrupted work.
When the actual state is stopped before finishing, the official continuation instruction is the appropriate reference. Keep a recovery attempt separate from a redesign request. Adding enemies, rewards or another level would make it harder to tell whether the unfinished work resumed.
The description of a paused state does not establish a Pause or Resume button. Follow controls that actually exist and the documented chat recovery. If the state remains ambiguous, preserve the observation rather than issuing repeated messages to force a response.
Examples
- State record: original request / explicit status text if shown / last content change / playable result observed or not / completion evidence / next decision. Unknown completion is not filled in from how long the screen has been open.
- Different outcomes: fresh scene elements are still appearing, so the observation is active output; a finished game lacks a requested goal, so the observation is a behavior mismatch. Neither is automatically a paused-generation case.
- Recovery scope: preserve the current game's request and use the documented continuation instruction without adding a second design goal to the same message.