I am reporting what appears to be a prolonged backend issue affecting the Content Maturity & Compliance review process for my experience.
I want to emphasize that this is not a request for instructions on how to complete the questionnaire, nor is it a case of a creator failing to satisfy the publishing requirements.
The questionnaire has already been completed and submitted.
The problem is that after weeks of communication with Roblox Support, multiple escalations, supervisor involvement, a re-submission specifically requested by Roblox, and subsequent review requests, the process still has not been completed and no actionable explanation has been provided.
At this point, I believe the history of this case demonstrates a failure somewhere in Roblox’s internal review workflow.
Timeline
The issue originally began in late July 2026.
Roblox Support investigated the experience and the associated eligibility/dashboard behavior. The case was subsequently escalated internally.
A Roblox Support supervisor acknowledged that the problem had persisted for some time and stated that the case had been escalated to the appropriate team.
Another supervisor subsequently described the underlying problem as a known issue that Roblox was actively investigating.
During the investigation, there were also significant inconsistencies between Roblox’s own systems.
At different stages of the case:
the Creator Dashboard appeared stuck at approximately 25 unique users;
Roblox Support stated that their backend showed 65 unique users;
the Creator Dashboard subsequently displayed approximately 80 unique users.
This already suggested that the issue was not simply caused by something I had configured incorrectly.
On August 6, a Roblox Support supervisor gave me a specific instruction to retake the Content Maturity & Compliance Questionnaire.
The same response explicitly stated:
“Once approved, the experience will automatically be set to everyone.”
I followed this instruction immediately and submitted the questionnaire again.
From that point onward, there was effectively nothing further for me to complete.
The remaining action was on Roblox’s side: review the submitted questionnaire.
What happened afterwards
The questionnaire remained pending.
I contacted Support again and specifically requested confirmation that the submission had been received, an explanation of what was preventing approval, and—if necessary—a manual review.
Instead of resolving the pending review, I repeatedly received responses asking for troubleshooting information that did not correspond to the actual problem.
Most notably, Support repeatedly requested a screenshot of the “last error message.”
There is no error message.
The questionnaire submits successfully.
The problem is that Roblox does not complete the subsequent review.
I explicitly explained this and even offered to provide screenshots of whichever specific page Roblox needed—the eligibility page, questionnaire status, Creator Dashboard, or anything else that could assist the investigation.
At another point I was informed that Support was unable to provide any further information regarding the inquiry, while the same response once again requested a screenshot of an error message that does not exist.
I subsequently used the available review/re-review mechanism and requested manual intervention.
The questionnaire remained pending.
I submitted a formal escalation.
The issue remained unresolved.
I opened additional Support requests because the original support process was no longer producing an actionable resolution.
One of those requests initially resulted in me being sent general documentation explaining that public experiences require a completed Content & Maturity Questionnaire.
That was particularly concerning because the entire reason for contacting Support was that the questionnaire had already been completed and was awaiting Roblox’s review.
Only after explicitly correcting this misunderstanding again was the request forwarded for “further review.”
I have now spent weeks attempting to get a submitted questionnaire reviewed.
Why I believe this requires engineering/internal investigation
At this point, repeating the standard questionnaire instructions cannot resolve the issue.
I have already:
completed the questionnaire;
resubmitted it when specifically instructed to do so by a Roblox Support supervisor;
waited for review;
requested manual review;
used the available review/re-review process;
provided the information requested by Support;
explained repeatedly that no client-side error message exists;
had the case escalated multiple times;
communicated with supervisors;
opened additional Support requests after the original process failed to produce a resolution.
Roblox Support itself previously acknowledged an underlying issue and escalated the case.
Nevertheless, the review remains unresolved.
There is no remaining troubleshooting action that has been identified for me to perform.
If something about my submission prevents approval, I need Roblox to identify what it is.
If the submission is valid, I need the review to be completed.
If the review job is stuck internally, I need it to be reset or manually processed.
Simply leaving the questionnaire pending indefinitely while repeatedly redirecting me through the same Support workflow cannot be considered a functional resolution.
Expected behavior
After submitting a valid Content Maturity & Compliance Questionnaire, the submission should eventually reach a definitive state.
It should either:
be approved;
be rejected with an actionable reason;
require additional information from the creator; or
produce an identifiable technical error that can be investigated.
Actual behavior
The submission remains pending without an actionable explanation.
Repeated review requests and Support escalations have not completed the process.
Support has previously confirmed that once the questionnaire is approved, the experience will automatically be set to Everyone, yet weeks later the prerequisite review itself remains unresolved.
Impact
This is not merely a cosmetic Creator Dashboard issue.
The unresolved review directly affects the experience’s intended availability and distribution.
For a creator, prolonged restrictions on an experience’s audience during an important release/update period can have a substantial effect on discovery, player acquisition, retention momentum, and the effectiveness of marketing.
This is precisely why the length and handling of this case are concerning.
A temporary technical problem is understandable.
What is much harder to understand is a technical problem persisting for weeks while the creator follows every instruction provided, the issue is repeatedly escalated, multiple Support representatives become involved, and yet the process ultimately returns to the same unresolved state.
Requested resolution
I am requesting that Roblox staff investigate the actual backend state of this questionnaire/review, rather than redirecting this report to another generic questionnaire troubleshooting article.
Specifically, I am requesting:
Verification that the submitted questionnaire is correctly present in Roblox’s review system.
Identification of whatever is preventing the review from completing.
Manual processing/resetting of the review if the automated workflow is stuck.
Completion of the review so that the previously stated Everyone availability can take effect if approved.
A concrete explanation if there is any legitimate outstanding requirement on my side.
I can provide Roblox staff privately with the affected Experience ID, Support ticket numbers, screenshots, and the complete Support correspondence documenting the case.
Request regarding the impact of the incident
Considering the exceptional duration of the issue and the amount of unsuccessful Support interaction required to reach this point, I would also ask Roblox to consider providing 150 Ad Credits as a goodwill credit once the underlying problem has been resolved.
I am not presenting 150 Ad Credits as a calculated monetary damages claim.
I am requesting them as a reasonable platform-side goodwill measure that could help the experience rebuild traffic and visibility after weeks during which its intended distribution has been affected by an unresolved Roblox-side process.
This seems particularly appropriate considering that I followed the instructions provided by Roblox Support, including resubmitting the questionnaire when specifically requested, and continued cooperating throughout the investigation.
I understand that the engineers or DevForum staff handling this bug report may not have authority to issue Ad Credits.
If compensation is handled by another Roblox team, I would appreciate this portion of the case being forwarded to the appropriate team rather than simply disregarded.
Final note
I am posting this report because the normal Support process has been exhausted without producing a technical resolution.
I am not asking DevForum staff to troubleshoot something I have not attempted to resolve through the appropriate channels.
I have spent weeks using those channels.
At this stage, I am simply asking for someone with access to the relevant system to examine why a questionnaire that Roblox Support specifically instructed me to submit still cannot complete its review process.
I would greatly appreciate an actual technical investigation and final resolution.
Expected behavior
After a valid Content Maturity & Compliance Questionnaire is submitted, Roblox should process the submission within a reasonable period and return a definitive review result.
If the questionnaire is approved, the experience should automatically become available to Everyone, as Roblox Support explicitly confirmed in my case.
If the questionnaire cannot be approved, the creator should instead receive a clear and actionable explanation identifying what must be corrected.
A submitted questionnaire should not remain indefinitely pending after resubmission, re-review requests, manual review requests, and multiple internal Support escalations.
In this case, I expect Roblox to inspect the backend state of the affected review, resolve or reset whatever is preventing it from completing, manually process it if necessary, and allow the normal approval workflow to finish.
A private message is associated with this bug report