HTTP 500 Error on Catalog Items, Presumably Due to Mass Deletions

Recently, Roblox moderation practices have been significantly updated, leading to mass deletions of copied faces. Due to the large volume of removed assets, some items (both deleted and not deleted) appear to be bugged rather than properly redirected to the main catalog page. Instead of these items loading properly (or redirecting to the catalog page if deleted), the assets return a HTTP 500 Internal Server Error, as seen in the attached screenshot.

This behavior makes it unclear whether the item is available, deleted or simply stuck in a bugged state. Affected users are left unsure if the asset is still available, gone permanently or if it is in an inconsistent moderation state.

Steps to Reproduce:

  1. Visit the link of an affected item. For example, this one: Err Face - Roblox
  2. Instead of redirecting to the main catalog page or displaying the item details if available, an HTTP 500 error appears.

Expected Behavior:

Deleted or moderated faces should redirect users to the main catalog page as expected, and available items (which are apparently also affected by this issue) should display normally.

I’m ~90% sure this issue stems from the mass deletions that have been happening in the past hour or two under the new moderation policies. This may indicate an overload or incomplete database updates during the moderation process.

Recommended Fix:

  • Ensure that all deleted faces are correctly redirected or marked as deleted in the catalog.
  • Ensure that available, non-moderated items load properly and do not display this error.
  • Investigate whether these assets are fully removed from the database or stuck in a moderation limbo state.

CC @BrightYellowElephant

A private message is associated with this bug report

1 Like

I’ve heard from others that this is also happening with normal, non-deleted items. Here’s an example: https://www.roblox.com/catalog/96508819035206/Glitched-Pirate

It seems the root domain is the error here:

This seemed to be a temporary outage as it’s now resolved itself. Regardless, some comment from an engineer would be nice to reaffirm this has been acknowledged :upside_down_face:

Happy to acknowledge here. The expected behavior is a redirect to the catalog home page when trying to directly access a moderated item.

We had a brief outage on Friday Feb 7 PST AM, but catalog has been healthy since (and it is healthy now).

Thanks for the report.

2 Likes