Hello, ever since Roblox had a few outages like, 3 days ago, I’ve been unable to publish/list any item as a “Limited item”
I have heard of a few work-arounds in the UGC Guilded server, about using a different browser. I have however, tried multiple browsers and 2 different machines/PCs as well!
I’m unsure why this happens, BUT it also seems to happen with a particular Dynamic head Bundle as well.
(I have enough funds to pay for the UGC’s copies, so funds shouldn’t be the issue)
HOWEVER, the issue with the limited items seems to happen on ANY UGC accessory I try to publish/list as a limited item.
Like I previously mentioned, I tried different browsers and nothing helped, and I also heard there’s more creators facing the exact same issue, so would be amazing if anything can be done about this as soon as possible!
I was experiencing this issue a few weeks ago (at the very least on 10/07) as well. It takes multiple hours of trying occasionally to publish limiteds in order to get them up, making it a massive inconvenience when I plan to release an item/plan my schedule around them but am unable too.
I’ve tried to give it a few hours and even days, but seems like the issue will keep occurring. I’m gonna try every few hours to publish, but honestly, this shouldn’t happen to begin with, so would be nice if a roblox staff could take a look into this and maybe have this issue noted so we won’t have this struggle, at this rate, public UGC might either crash the roblox avatar service, marketplace, or the website as a whole, and by the looks of it, roblox isn’t prepared to handle almost 2 million users in one game, let alone more than a million, able to publish Limited UGC items
Also occurring with me! Here are my details:
Putting on-sale from a group (6235152)
I uploaded the asset (15133744653)
I am attempting 0 price, 1,000 quantity, 1 copy maximum per user, and in-experience via API only. Works on no browsers, not on my phone, etc. My user is is 35323013 (this account).
Hi all - thank you so much for your patience on this. We’ve been working diligently on this since yesterday when it started around noon PST and are happy to report the team fixed this a few hours ago.