if you still have that amount of robux in your account, it’s completely possible to submit a request for devex - the eligible robux indicator isnt always accurate
I have been getting this issue too, and has been happening for the last 5 months at least. It seems to be a visual issue but still a very annoying bug…
Hi there, thanks for reporting this. We are currently investigating this.
Blockquote
if you still have that amount of robux in your account, it’s completely possible to submit a request for devex - the eligible robux indicator isnt always accurate
This is correct - the eligible amount of Robux you have does not impact your ability to actually use DevEx.
Thanks for the clarification! I’ll keep the topic open until the issue is fully resolved.
Hey, I’ve already reported this before and my thread has received activity very recently.
Edit: Seems like it’s been closed
Yes, please read:
I confirm that this is only a cosmetic bug, I also had it shown that there was 0 robux eligible and yet I managed to cash out without any problems.
I’m experiencing the same bug for the 4th time now — I really hope it gets permanently fixed this time. Also, I have no idea where the 2000 Robux comes from when this bug happens.
This happens quite often, ive seen it before and the request still works.
You should now see an accurate estimate, Tomtom4500. We expect it to be resolved for everybody within the next few hours. Please confirm in the thread - I’ll wait until its resolved for everybody before marking this as completed.
It’s been almost two hours since your reply, and the issue still hasn’t been resolved on my end. I’ll be going to sleep soon as it’s already past 5 a.m., so I’ll follow up with you once I’m awake.
Hi, I am still getting the 0 Robux Eligible issue for me still, been 2 hours since as well.
Just wanted to let you know it’s still the same.
On my end it looks like your estimate has been updated - mind checking one more time?
Let me investigate your case - yours still appears incorrect.
I forgot to mention, but this is for a different account of mine. I sent the user ID via DM — the bug is still ongoing there.
That account and kni0002 both have the same root cause - working on getting that resolved
Appreciate the patience here, we’re working on some improvements that should make the estimates more reliable going forwards.
Alright, things should be resolved for everybody now. Sorry for the delay.
Once I have confirmation, I’ll transition this thread.
Yeah, it seems to be fixed now — hopefully I won’t have to come back here again.