Duplicate moderation review of identical image asset escalated account to termination; appeals response cites conduct not on record

The moderation system reviewed the same image file twice as two separate violations, 70 minutes apart, and counted the second review as a “repeated violation,” escalating the account (shuxshu3) straight to termination. Both copies of the file were uploaded together as part of one development task (a decal and a Developer Product icon for the same game) BEFORE the first moderation action existed — no activity occurred between the two flags; the queue simply processed the second copy later.

Steps that cause the bug:

  1. Upload the same image file twice as part of one development task (decal + Developer Product icon).
  2. The first copy is moderated — Aug 5, 2026, 3:34 AM: Violation ID 3HUcRi4tD06LqhwKLwwODbXNIW5, Asset ID 95102184811974, “Harmful Content/Behavior.”
  3. The second copy, already uploaded before any moderation notice, is reviewed 70 minutes later — Aug 5, 2026, 4:44 AM: Violation ID 3HUkwHfntrcqV1pucyDh1gl6s0t, Asset ID 121312447903707 — and counted as an escalating repeat offense, terminating the account for “repeated rule breaking.”
  4. The prior strike the escalation relied on (Jul 31, Violation ID 3HHaAT8oLgiGnLeE2FlnDkizkMt) is later overturned on appeal (accepted Aug 5, 12:36 PM — “didn’t break the rules”), but the termination is never recalculated.
  5. The appeals ticket response (Aug 7, 7:15 AM UTC) states the account was moderated for “sending messages to other users” — no messaging violation exists on the Safety Dashboard; both entries are asset uploads.

After I replied to the appeals ticket documenting the record mismatch (violation IDs and timestamps above), the ticket was closed 54 minutes later (Aug 7, 8:09 AM UTC) with “we’re unable to provide any further information or response,” without addressing any of the documented discrepancies.

Screenshots of the ban screen and both dashboard violation entries are attached. The removal of the image itself is not being contested — this report concerns the duplicate-count escalation and the appeals mismatch only. This matches previously reported defects, e.g. “Account moderated for the same asset multiple times leading to termination” and “Account Terminated Due to Duplicate Moderation Review.”

Expected behavior

Two automated flags on the same image file, both copies uploaded before any moderation notice was issued, should be consolidated as one incident — not counted as escalating “repeated” violations. Escalation for “repeated rule breaking” presupposes the user continued after being notified; here, all conduct predated the first notice. Additionally, when a prior violation used to escalate a penalty is overturned on appeal, the escalated penalty should be recalculated. Appeals responses should reference the conduct actually on the account’s record.

SafetyDashboard3.pdf (182.0 KB)
Gmail - Roblox Support Ticket 178724956.pdf (155.3 KB)
SafetyDashboard2.pdf (572.0 KB)
SafetyDashboard1.pdf (544.0 KB)

A private message is associated with this bug report

3 Likes