16 days ago
Workspace id: 5b30980f-e158-4201-8cbf-bdf64ba3704f
Unsure if this is an actual issue, interpreted it as such + was told to create a #✋｜help by lovely uxuz
Has been in this state pretty much ever since the rollout of the new limits
Problem:... shouldn't it be 32 vCPU/RAM?
Attachments
6 Replies
16 days ago
This thread has been escalated to the Railway team.
Status changed to Awaiting Railway Response Railway • 16 days ago
16 days ago
I've put you back on 32/32
15 days ago
You're right, your workspace should be 32/32, and you've been put back. The cause: a billing/subscription event was incorrectly bumping grandfathered Pro accounts (like yours, from before the new-limits rollout) to the newer 24 vCPU/GB version. We have a fix in review that stops billing events from touching your limits version, so it won't reset on you again. Thanks for flagging it. — Angelo
Status changed to Awaiting User Response Railway • 15 days ago
15 days ago
Follow-up: the fix for this just merged, billing and subscription events will no longer bump grandfathered Pro accounts off the 32/32 limits. You're set at 32/32 and it'll stay there now. Thanks for flagging it. — Angelo
15 days ago
incredible, back to 24
Attachments
15 days ago
Okay, I will look into this.
14 days ago
You are back on 32/32, and I have merged a fix that will prevent the limits downgrade from happening again.
7 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 7 days ago