a month ago
Hello,
I need help removing an explicit service-level Replica Limits / resource limit override from a staging service without triggering a deployment.
Project ID:
246aad08-8292-4a89-90b9-bddf30ee52f7
Environment ID:
a072e11d-1ba5-4009-8168-930ceec9256f
Service ID:
657a0b85-d46b-4b05-9a13-9efb10d816c1
Service Instance ID:
d06ffc0b-4402-4b94-b5a8-c9022d9dbbbe
The current explicit environment configuration contains:
services..deploy.limitOverride.containers = {
cpu: 8,
memoryBytes: 8000000000
}
I need deploy.limitOverride to become absent/null so the service inherits the workspace/plan defaults.
I already tried a public EnvironmentConfig patch with:
deploy.limitOverride = null
and committed it using:
environmentPatchCommitStaged(..., skipDeploys: true)
The operation completed without creating a deployment.
However, authenticated readback showed that Railway normalized the property back to:
{
cpu: 8,
memoryBytes: 8000000000
}
instead of removing the explicit override.
I also checked the current public GraphQL schema and could not find a documented clear/remove/reset operation for this property.
In the Railway dashboard, this service also does not show a Replica Limits section under Settings → Deploy.
Could you please tell me the supported way to completely remove the explicit deploy.limitOverride and restore inherited/default plan limits WITHOUT creating a deployment?
If this requires a Railway-side action, please let me know.
Thank you.
1 Replies
a month ago
The values you are reading back (8 vCPU / 8 GB memory) are the Hobby plan's default per-replica resource caps, not an explicit override on your service. Your workspace has no override config set, and the service itself carries no limit override in its committed configuration. The API returns the plan defaults when no explicit override exists, which is why patching to null and reading back still shows the same numbers. There is nothing to remove here because the service is already inheriting the workspace/plan defaults.
Status changed to Awaiting User Response Railway • 28 days ago
21 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 • 21 days ago