BC-0202 · TROUBLESHOOTING
Editorial review 2026-09-26
Roblox Build Prompt Rejected
A rejected prompt, a failed send and an unwanted generated result need different responses. Start with the actual message and the stage where it appeared. Do not label a generic error as a content violation, or try disguised versions of a request that was explicitly refused on safety grounds.
Symptom
A request appears rejected, but the stage and meaning of the response have not been established.
Immediate action
Preserve the exact notice and whether the request or result was visibly acknowledged.
Diagnostic branches
- The response expressly identifies a content restriction.
- Use compliant redesign guidance without disguising the prohibited element.
- No send acknowledgement or result is visible.
- Keep sending or connection failure distinct from a moderation finding.
- Generation stopped after acknowledgement.
- Use documented unfinished-generation recovery rather than inventing a refusal reason.
- A game exists but differs from the brief.
- Describe the actual missing behavior and use a bounded output repair.
Least-destructive change
Select the appropriate existing troubleshooting branch from visible evidence before sending another request.
Retest
- The classification quotes the actual notice rather than a guessed cause.
- Existing output is not discarded to reproduce the same message.
- Unknown stages and unperformed checks remain explicit.
Escalation
Ask official assistance to clarify an unresolved notice using existing evidence. This checklist does not determine moderation policy, promise acceptance or authorize bypassing a refusal.
Working notes
Keep the exact response alongside the request it concerns. A notice shown before any acknowledged send is not the same evidence as a refusal after the request was accepted. If the interface does not make the stage clear, mark it unknown rather than inferring a moderation decision from the lack of a game.
An explicit content or intellectual-property refusal belongs to the blocked-prompt guide. Its safe next step is substantive compliant redesign, not spelling substitutions or alternate accounts. A generic connection or generation error does not establish that the prompt's theme is prohibited; keep that uncertainty in the report.
If a playable result exists, compare it with the requested behavior. A different layout or missing mechanic is an output-quality issue unless the actual response says otherwise. Do not replace a bounded repair with a series of attempts to discover an imaginary list of forbidden words.
Choose the route once the observation is classified: documented recovery for stopped output, access or sending checks for an unacknowledged request, policy-safe rewriting for an explicit refusal, or behavior repair for an existing result. If the notice cannot be classified, preserve it for official assistance without repeating paid attempts just to force a clearer message.
Examples
- Stage record: intended request / whether a send was visibly acknowledged / exact response / whether any result exists / remaining uncertainty. An empty result field is not evidence that the request was policy-blocked.
- Classification contrast: 'the game runs but the gate never opens' is a behavior discrepancy; a response explicitly refusing the requested theme is a content-boundary result. Neither description should be substituted for the other in a report.