Setting 'Usage Limit' is inconsistent

[jankeromnes]

Bug description

Setting the 'Usage Limit' for a newly subscribed team is inconsistent:

Steps to reproduce

1. Upgrade a team to Usage-Based
2. Set a custom Usage Limit
3. Reload the page 🎰 Usage Limit now has a different value!

Workspace affected

No response

Expected behavior

The 'Usage Limit' should still have the value that you set, not some other random value.

Example repository

No response

Anything else?

• When testing [UBP] Remove team specific Stripe APIs from server JSON-RPC API #12957, I noticed an unrelated problem: [UBP] Remove team specific Stripe APIs from server JSON-RPC API #12957 (comment) -- I subscribed a new team, changed the usage limit from 100 to 200, refreshed... and my limit was suddenly 0 (with a limit reached alert) 🤔
• Then I tested something similar: [UBP] Remove team specific Stripe APIs from server JSON-RPC API #12957 (comment) -- I subscribed as an individual, changed the usage limit from 100 to 200, refreshed... and my limit was suddenly 500 🤪
• Then, I tested again on https://gitpod-staging.com (see above YouTube video) -- subscribe as a new team, change limit from 100 to 200, refresh... and suddenly my limit was 100000 🤯

Is it somehow getting the limit from a different team? 🤔

[svenefftinge]

Looks like a race. The 1,000,000 credits are set as a default when there is no cost center.

[jankeromnes]

I can take a look at this issue while implementing #13389 👀

[jankeromnes]

I can no longer reproduce this issue. Maybe it was fixed meanwhile?

Let's close this for now, and re-open if it comes back. 🧟