Skip to content
Subject: GraphQL projectCreate failed — need confirmation of request outcome
lynxdabliu
OP

3 hours ago

Hello Railway Support,

We are integrating Railway's GraphQL API into our infrastructure management platform.

On November 16, 2026, at approximately 18:47:43 UTC, a projectCreate mutation returned a GraphQL error.

Request details:

  • Operation: projectCreate
  • Endpoint: https://backboard.railway.com/graphql/v2
  • Our X-Request-ID: 3700ff37-a699-4306-b608-ead7f6b44636
  • Token type: Workspace API Token
  • Intended workspace: Plain Group infrastructure workspace

The original GraphQL error response was not retained, so we no longer have its traceId.

Subsequent read-only checks confirm that the token can access the workspace, list its two existing projects and introspect the ProjectCreateInput schema.

However, no new project is visible, and our system has blocked further attempts to prevent duplicates.

Could you please confirm:

  1. Whether Railway received the original request.
  2. Whether a project was created or the mutation was rejected.
  3. If rejected, the reason and available error details.
  4. Whether the original request can be located using our timestamp and X-Request-ID.

We can provide the workspace UUID and further request details privately.

We need confirmation before safely retrying the operation.

Thank you.

Solved

2 Replies

Status changed to Awaiting Railway Response Railway • about 3 hours ago


Railway
BOT

3 hours ago

We located that request by your X-Request-ID: it reached us at 18:47:43 UTC on November 16 and was rejected with a validation error, "Project names must be between 1 and 32 characters." No project was created, and no project has been created or deleted in that workspace since, so it is safe to retry once the project name is between 1 and 32 characters.


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


lynxdabliu
OP

3 hours ago

Hello! Solved! Thank you!


Status changed to Awaiting Railway Response Railway • about 3 hours ago


Status changed to Solved lynxdabliu • about 3 hours ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...