Free plan resource provision limit exceeded — need exact limit clarification
rizwan1030
FREEOP

12 days ago

I’m trying to provision a PostgreSQL service in an existing empty Railway project, but Railway returns:

“Free plan resource provision limit exceeded. Please upgrade to provision more resources!”

I need clarification on the exact resource counter and scope that is blocking this operation before I delete resources or change my plan.

Workspace ID:

503c0e70-7db9-494b-9d24-1e928408dd1a

Target project:

SustainX-A7-Staging

Target project ID:

7b1fe19b-3ecb-408c-a35d-bad0bc3188b7

Target environment:

a7-staging

Target environment ID:

a14f3b46-3b2b-49a9-a460-cd449870a339

Failed operation ID:

a43e6b6c-3d76-45c9-b66a-73c93e896ed6

Operation:

PostgreSQL template deployment into the existing target project/environment.

Current target-project inventory:

  • Services: 0
  • Databases: 0
  • Volumes: 0
  • Deployments: 0

Workspace metadata currently reports:

  • Plan label: HOBBY
  • Trialing: true
  • Subscription state: INACTIVE
  • Active subscriptions: 0
  • Projects: 2
  • Exposed project limit: 2
  • Exposed service limit: 5 per project
  • Exposed volume limit: 3 per project
  • Remaining account credit: approximately $4.35

An important inconsistency is that:

  • workspace resourceAccess.project.disallowed returns the same “Free plan resource provision limit exceeded” message;
  • the workspace is at 2 projects out of its exposed limit of 2;
  • however, databaseDeployment.disallowed for the target project is null;
  • the target project itself has zero services and zero volumes.

Could you please tell me:

  1. Which exact provisioning counter rejected operation a43e6b6c-3d76-45c9-b66a-73c93e896ed6?
  2. Is the limit workspace-wide, project-wide, trial-wide, service-related, database-related, volume-related, or something else?
  3. What are the current and maximum values for that counter?
  4. Is the workspace’s 2/2 project count involved in this PostgreSQL template failure?
  5. I have an unused PostgreSQL service in another non-production environment. Would deleting that service and its volume actually release the blocked provisioning capacity?
  6. Can this PostgreSQL service be created under the current trial without upgrading, and if so, what specifically must be changed or released?

I do not want to delete resources or upgrade based on guesswork, so I’m looking for the exact backend limit associated with this failed operation.

Thank you.

1 Replies

rizwan1030
FREEOP

9 days ago

Following up on this provisioning failure. The key question is which exact limit rejected operation a43e6b6c-3d76-45c9-b66a-73c93e896ed6. Would removing the unused PostgreSQL service and volume from a separate non-production environment release that limit? I’d like to confirm before deleting anything. Thanks.


Welcome!

Sign in to your Railway account to join the conversation.

Loading...