Bundle Claims in Rights Manager Fail to Load Properly — Reported Creation Shows as Deleted and Breaks Comparison View

When submitting a Claim through the Rights Manager Claims page targeting a bundle, the “Reported Creation” fails to load correctly.

Instead of being marked offsale (as expected), the bundle appears as if it has been deleted or is otherwise inaccessible. This completely breaks the Creation Comparison functionality — the reported asset’s image does not load, and neither the reporter nor any party involved in the claim process is able to visually compare it against their own content.

This does not happen with other asset types such as images — they display correctly and allow for proper comparison. This issue appears to specifically affect bundles, and potentially other UGC asset types.


Where It Happens:

Rights Manager Claims page, specifically when submitting claims against bundles.


When It Happens:

Issue consistently occurs as of July 8, 2025, and reproduces every time a bundle is reported.


Steps to Reproduce:

  1. Go to the Rights Manager Claims page.

  2. Start a claim and provide the link to any bundle (e.g., a head bundle) as the Reported Creation.

  3. Submit the claim.

  4. Once the claim appears in the list, click on the claim entry itself to open the detail view.

  5. Observe the following issues:

    In the list view:

    • The bundle’s image thumbnail fails to load.
    • The bundle’s ID is visible, but the text “Could not fetch creation” appears underneath.

    In the detail view:

    • The Reported Creation still does not load visually.
    • It appears as if the item was deleted, rather than simply offsale.
    • Creation Comparison is unusable, as the bundle’s image is missing and cannot be compared side by side with your own content.

:lock: Note: You must be part of the Rights Manager Claims Beta to access this page and view submitted claims.


Expected Behavior:

  • The bundle should appear offsale, not as if it were deleted.
  • Its thumbnail and metadata should load normally.
  • Reporters should be able to see the reported asset clearly within Creation Comparison for visual assessment.

This is essential for users to confirm whether a report is valid or not.


Reproduction Rate:

100% — issue occurs every time a bundle is used as the Reported Creation.


System & Browser Info:

  • Browser: Opera GX 119.0.5497.144 (Chromium 134.0.6998.205)
  • Operating System: Windows 11 Pro
  • Processor: Intel Core Ultra 9 275HX
  • Memory: 64 GB RAM
  • Graphics: NVIDIA GeForce RTX 5090

(Issue occurs even with all browser extensions disabled)

Page URL: https://create.roblox.com/dashboard/rights-manager/claims

1 Like

Hey, I believe this is happening because you don’t legally own any of the rights to these heads designs. Hope this helps!

All of my claims were accepted, so that’s not the case here. Also, if they have the rights to use that content, they’re fully entitled to dispute the claim, and what you said isn’t relevant to the issue at all.

Also, fun fact — the reason your head isn’t getting fetched is probably because it was claimed by Epic Games under an external IP flag. When that happens, Roblox doesn’t just mark it as offsale — it completely wipes it from the preview system. Both the original and the reported items show up as “Could not fetch creation,” so no one can even see what was claimed.

So yeah, if you’re wondering why your stuff disappeared from the claim view, it’s not a glitch — it’s Fortnite telling Roblox, “this is ours now.”

Also, just to clarify — the reason your head isn’t being fetched is because it was claimed by Epic Games under an external IP. When that happens, Roblox doesn’t just mark the item offsale — it scrubs it from the preview system entirely. Both the reported and original assets get hit with the “Could not fetch creation” error, making them completely unviewable.

So anyway, this is a situational case where your item was externally claimed. That’s not a bug — that’s just how Roblox handles third-party IP takedowns.