Skip to content
Replica limits fail to stage on new services before first deployment
laurentduhamelosteo-byte
OP

2 hours ago

On Railway Hobby, two GitHub-backed services and their volumes are still staged for creation. Saving a CPU limit from Settings → Replica Limits shows “Error: Staging changes”, and a reload restores the default. A staged service update returned “Service Instance not found”. What supported procedure lets us create the service instances without deploying source code or provisioning volumes, then verify CPU and RAM limits before the first deployment? Can the existing staged work be preserved or must the sources and volumes be staged separately?

Awaiting User Response

1 Reply

Railway
BOT

2 hours ago

Service settings like replica limits can't be saved on a service that is still only staged for creation, because its service instance doesn't exist until the creation is applied. That is why you see "Service Instance not found" and the limit disappears when you reload.

The supported order is to create an Empty Service with no source and click Deploy to apply just that creation. Then set the CPU and RAM limits in the service's settings and click Deploy again to apply them. Connect the GitHub repository and add the volume only after that. Applying a service with no source does not start an application deployment, so only the final Deploy builds and runs your code, using the limits you already set.

Your current staged changes can't be reused for this. Deploy applies everything staged in the environment, so applying it now would attach the repositories and provision the volumes along with the services. Discard Changes also removes the whole staged changeset, because there is no way to discard individual changes. To follow the order above, discard the current changeset, then stage the empty services, their limits, and finally the sources and volumes as separate applied steps.


Status changed to Awaiting User Response Railway • about 2 hours ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...