Hey, thanks for responding. It seems that this issue is being corrected and now the endpoint sends a response with at least some eligible Robux, but it is still lower than it was before.
Here’s an older image:
Keep in mind, I’ve never DevEx’d nor spent these Robux.
Thanks beforehand!
Please hold, the system is still churning the latest data. I’ll let you know when to look again.
This should be resolved now. I confirmed your estimated eligible Robux value seems correct again. We’ll take some measures to avoid this regressing again. Thanks for reporting this.
That’s weird, I recently made 4501 robux from a gamepass sale 2 weeks ago, For some reason, only around 8% of the robux I earned is devex eligible.
I spent a little bit of robux i earned, but still:
Since your fix, my eligible Robux amount got stuck at 2000. I earn all my revenue from UGC sales, and it used to work before, but now it’s broken.
The fix seems to have worked for me! All my Robux are showing as eligible to be cashed out, which was the original behavior before this issue arised. Thanks.
Unfortunately I’m still having this issue. All my robux come directly from UGC sales. The amount still shows as 0 for me. It used to show all my Robux.
Thanks @JojogamezYT @raskolibov @010DevX101 @GaelPaws for bringing this up, unfortunately it looks like this is a different issue happening in a different point in the system than the original issue here. One of the sources of data is missing for the most recent date.
I’ve asked the internal team that owns that data to take a look at it, but for now again this should not block you from DevExing if you need to. I’ll update here when it is resolved.
Hey @JojogamezYT @raskolibov @010DevX101 @GaelPaws this is also fixed now AFAIC, thanks for bringing it up.
I just checked again and it’s been resolved. Thank you for your time.
Amazing, thank you for your time!
A Week later, it is still happening to me. i have 17k Eligible that came from one of my games, and it was working 2 days earlier, but just yesterday it started showing 0 after a second.
Yup. Can confirm it’s happening again.
Happening again for me as well. Disappointing
The issue is occurring again for the third time — I hope something definitive is done about it.
Hi, the improvements I referred to have not been shipped yet (they are going out this week) and it looks like we have a regression in the mean-time that we didn’t notice yet. Sorry for the inconvenience. Doing some tweaks now.
For the future, please submit a new bug report for new instances of this issue, to ensure my team sees it in case I am not available.
There’s a newer report here:
Feel free to close one of them out,
FYI this report was still marked as “Open” when the issue popped up again, so you’d assume it was still open internally, eliminating the need for a new report, but guess not
This should be resolved now and the count will get a little bit more accurate over the next ~hour for a minority of users.
Thanks for bringing it back up. I’m going to set a tighter lock time on this thread now to encourage new bug reports for future issues.
It’s been fixed on my end — thanks, and hopefully it won’t resurface again, since it’s a very minor bug.
