DevEx Eligible Robux Dropped to 0 Despite No Spending

Bug Reports Roblox Application and Website Bugs
,
1

I am a small Roblox developer, and I recently encountered an issue with the Developer Exchange (DevEx) system. The estimated eligible Robux on the DevEx page (https://create.roblox.com/dashboard/devex) dropped from approximately 250,000 Robux to 0 in a single day, without me spending or using any Robux during that period. My account balance still shows about 250,000 Robux, but the amount eligible for DevEx now appears as 0.

Steps to Reproduce the Issue:

  1. Visit the DevEx dashboard: https://create.roblox.com/dashboard/devex
  2. Observe the “Estimated Eligible” Robux total.
  3. (Previously) the amount showed ~250,000 Robux.
  4. Without making any transactions or spending Robux, the eligible amount dropped to 0 the next day.

Visual Aids:
Screenshot of the DevEx page showing 0 eligible Robux:

image
image1414Ă—162 28.4 KB

Direct Links:
DevEx Dashboard: https://create.roblox.com/dashboard/devex

System Information:
Operating System: Windows 10 Pro 64-bit
Processor: intel(R) i5-1035G1 CPU
Memory: 8 GB RAM
Graphics: intel(R) UHD Graphics
Internet: Stable high-speed connection

Browser Information:
Browser: Google Chrome 123.0.6312.105 (64-bit)

Additional Info:
I also submitted a DevEx request for 30,000 Robux shortly after the drop (the button was still Blue at the time), and it is still pending currently. Since I did not use or move any Robux, I believe this may be a bug affecting the eligibility calculation. I would appreciate clarification and a refund of the eligible amount if this is indeed an error.

Best regards,
Tomtom4500

→ Edit: The bug is only visual and has no impact on the ability to actually use DevEx.

2 Likes
2

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

2 Likes
3

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…

image
image1032Ă—225 28.7 KB

1 Like
4

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.

5 Likes
5

Thanks for the clarification! I’ll keep the topic open until the issue is fully resolved. :slight_smile:

1 Like
6

Hey, I’ve already reported this before and my thread has received activity very recently.

Edit: Seems like it’s been closed :thinking:

2 Likes
7

Yes, please read:

2 Likes
8

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.

1 Like
9

image
image1516Ă—176 24 KB

Having this issue but it seems to be only a visual issue like the others said.

1 Like
10

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.

1 Like
11

This happens quite often, ive seen it before and the request still works.

1 Like
12

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.

3 Likes
13

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.

14

Hi, I am still getting the 0 Robux Eligible issue for me still, been 2 hours since as well.

15

Just wanted to let you know it’s still the same.

16

On my end it looks like your estimate has been updated - mind checking one more time?

17

Let me investigate your case - yours still appears incorrect.

1 Like
18

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.

19

That account and kni0002 both have the same root cause - working on getting that resolved :pray:

Appreciate the patience here, we’re working on some improvements that should make the estimates more reliable going forwards.

3 Likes
20

Alright, things should be resolved for everybody now. Sorry for the delay.

Once I have confirmation, I’ll transition this thread.

1 Like