Group ID 374156804 locked in backend cache loop post-appeal approval an account restored("An error occurred while retrieving group payouts")

[30/07 STILL NOT SOLVED] Hello, my primary account appeal was officially approved by Support (Agent Margarita), fully restoring my account 01_iiSantxs, main group and experiences. Closing my case when It´s not solved since my second group Del1cacy´s Angels, the one that generates the most - Group ID: 374156804 remains locked in a backend database cache loop, causing massive daily financial losses and blocking acces to more than 1,000,000 robux that are pending in that group.

-Group ID: 374156804
-Group Link: https://www.roblox.com/communities/374156804/Del1cacy-s-Angels
-Owner Account: 01_iiSantxs

Urgen Business And Financial Impact

  • 1M plus total robux frozen: Over 867,620 Robux in direct group balance ($3,296 USD) plus substantial pending Robux are completely locked.

  • High-Revenue UGC Catalog Archived: Dozens of top-performing face/UGC items under this group remains off-sale. A sinngle face item in this group alone was generating over 100,000 robux weekly. Loosig all the revenues. Having this UGC forced offline for nearly a month represents catastrophic, unrecoverable revenue loss for a creator.

  • Upcoming Official Roblox Event (August 8th): I have been officially invited to participate in an upcoming Roblox Creators Event on August. It is critical for my team to enter this event with the group assets, catalog items, and standing entirely cleared and operational to represent my two groups

-Technical Evidence (API Error)

When navigating to Group Configure and then Payouts, the backend fails to process data and displays the following internal API error: And error ocurred while retrieving group payouts.
This confirms the issue is not a moderation decision, but a backend status desynchronization where the approved appeal status failed to push to group ID 374156804

Expected behavior

I have always maintained strict compliance with Roblox Terms of Use. Since standard support channels are stuck in automated loops, I urgently ask an engineer or DevRel team member to execute a manual status/ cache force refresh on Group ID: 374156804 to clear the residual moderation flag and restore UGC and payout API functions
-Group ID: 374156804
-Group Link: https://www.roblox.com/communities/374156804/Del1cacy-s-Angels
-Owner Account: 01_iiSantxs
Thank you gor your assistance in resolving this critical technical blocker

A private message is associated with this bug report

1 Like

Thank you for the report. We have assigned to our team for review.

Can you help reach out to our Customer Support channel to help resolve this issue as they are better suited to help fix the issue. Closing for now but please don’t hesitate to reach out to us with any further questions.

1 Like

Hi @starhiker13

Thank you for looking into this. However, Customer Support HAS already reviewed and fully approved my appeal not resolving the case (Ticket handled by Agent Margarita, restoring main account 01_iisantxs).

The reason I opened this Bug Report is because Customer Support cannot fix backend database synchronization errors. Standard support representatives do not have access to execute a force cache refresh or resolve the group payout API error (“An error occurred while retrieving group payouts”).

Customer Support directed us back to the technical/DevRel channels because Group ID 374156804 is technically stuck in a desynced state post-appeal.

Could you please escalate this to the technical/engineering team who handles group backend data? Standard support cannot resolve backend API failures

1 Like

Hi @starhiker13 I have submitted the official Bug Report and opened Ticket #177774422 with Customer Support as requested. Support confirmed they cannot force cache updates directly, so could you please link Ticket #177774422 to the engineering team for a manual cache update on Group ID 374156804? Thank you!! I have 1,000,000 still in pending in this group and they’re completely frozen!!


1 Like

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.