17 minutes ago
Hello Railway team,
Our existing service duetgo-web runs in an active Hobby workspace. In Service Settings > Replica Limits, the dashboard shows CPU 0.25 vCPU and Memory 0.25 GB, with plan limits of 8 vCPU / 8 GB, but both resource sliders are disabled. The project membership page shows Can Edit for the current account.
Incident JUA1PC5H now says Hobby builds were re-enabled at 20:43 UTC on October 20. After returning to the correct service/environment, the Replica Limits controls remain disabled. We are not assuming that the build incident causes the resource-control issue.
What is the supported way to enable these controls for this existing service? We want to understand the restriction without upgrading the plan, recreating the service, changing access permissions or affecting its attached persistent volume. No resource change has been applied.
Thank you.
Service selector note: duetgo-web is not listed in this form, so N/A is selected only for routing. The question concerns the existing service described above.
2 Replies
16 minutes ago
The Replica Limits sliders can only be changed by someone with Admin access to the project (a project Admin or a workspace Admin), so an account with Can Edit access sees the current values but cannot move the sliders. This is unrelated to the build incident. The other case where they lock is when the service's resource limits are set in a railway.json or railway.toml config file, in which case that file controls them.
On our side, duetgo-web sits in a workspace your account is not a member of. So the change needs to be made by an Admin of that project or workspace, or that person can grant your account Admin access. Changing the limit does not require recreating the service and does not touch its volume.
Status changed to Awaiting User Response Railway • 16 minutes ago
Railway
The Replica Limits sliders can only be changed by someone with Admin access to the project (a project Admin or a workspace Admin), so an account with Can Edit access sees the current values but cannot move the sliders. This is unrelated to the build incident. The other case where they lock is when the service's resource limits are set in a `railway.json` or `railway.toml` config file, in which case that file controls them. On our side, duetgo-web sits in a workspace your account is not a member of. So the change needs to be made by an Admin of that project or workspace, or that person can grant your account Admin access. Changing the limit does not require recreating the service and does not touch its volume.
7 minutes ago
The issue is not resolved. Could a human from Railway confirm the exact permission required for Replica Limits?
The official Project Members page (https://docs.railway.com/projects/project-members) says Editors can change project settings. Our account shows Can Edit, while both Replica Limits controls remain disabled. Please clarify whether these specific controls require a project Owner/workspace Admin, and the supported next step for the current project access.
The affected service is also absent from the Central Station Service selector; the N/A routing note explains that limitation. We are not requesting an upgrade, permission change, service recreation or volume change. Thank you.
Status changed to Awaiting Railway Response Railway • 5 minutes ago