BC-0125 · TROUBLESHOOTING
Editorial review 2026-09-26
Roblox Build Age Check Keeps Reappearing
If an age-check request returns, compare the previous outcome with the new prompt before calling it a loop. Roblox says an estimated-age discrepancy can lead to another age-check prompt after an earlier check. That documented possibility does not diagnose the cause of every repeated request.
Symptom
An age-check request appears again or the account flow returns to the same request screen.
Immediate action
Compare the last observed completion state and the exact current prompt before trying again.
Diagnostic branches
- The earlier check never showed a completed outcome.
- Treat the result as unresolved and follow the official status or failure route.
- Completion was shown and a new explicit request appears.
- Preserve the new requirement and consult the current legitimate check guidance.
- A screen returns repeatedly without a result or explanatory notice.
- Record the screen transition and stop repeated submissions before seeking official assistance.
Least-destructive change
Keep verification status intact while documenting the request sequence; do not undo a check merely to experiment.
Retest
- Confirm that the earlier and current observations concern the same account.
- Differentiate an explicit new requirement from an unexplained returned screen.
- Keep the documented discrepancy possibility separate from an asserted diagnosis.
Escalation
Use Roblox's official age-check help with the redacted sequence and exact notice if the displayed path cannot be completed. Do not send identity images to public forums or this guide site.
Working notes
Preserve the sequence, not the sensitive material used in the check. Record whether the earlier flow displayed completion, whether the account stayed the same and what action triggered the new request. A request after an unconfirmed submission is different from a new request after a confirmed result.
Read the latest prompt on its own terms. It may describe an available next step or a specific requirement. Do not keep restarting an older flow just because it was the route used previously, and do not substitute another person's document or verification result.
Distinguish a repeat requirement from a navigation loop. If the same screen returns without an outcome after an action, record that screen transition. If the account explicitly asks for another check, record the requirement. Neither observation proves fraud detection, a camera fault or a hidden account penalty.
Stop repeated submissions when the outcome remains unclear. Use current official age-check assistance with a redacted sequence. This guide does not collect identity documents, estimate age or offer an alternative verification service.
Examples
- Sequence A: submission attempted → no completion shown → request still present. Completion remains unconfirmed; the evidence does not yet show that an accepted result was revoked.
- Sequence B: completion shown → later Build access attempt → new age-check request. Preserve both messages and use the current request's legitimate path without claiming a specific backend reason.
- Screen-loop record: selected action / screen reached / outcome text or its absence / screen returned to. The record localizes the repeated transition without sharing the capture itself.