6 hours ago
I need provider-side confirmation of the terminal state of a specific Railway projectCreate GraphQL mutation.
Requested project name: guixu-cloudbook-g09-validation-v1-001
Client operation started (UTC): 2026-09-08T14:50:14.921495Z
Local operation ID: 879477ca-d14c-4fb5-a4c0-e2e8f2ed892c
This is a client-local operation ID, NOT a Railway request ID.
Submitted description marker: GUIXU_CLOUDBOOK_G09_RAILWAY_SYNTHETIC_VALIDATION_V1_001:879477ca-d14c-4fb5-a4c0-e2e8f2ed892c
The first projectCreate returned GRAPHQL_ERROR. The client did not preserve the Railway traceId or provider request ID.
Subsequent authenticated reconciliation showed:
- 0 active projects.
- No matching deleted project.
- No matching audit event.
- Repeated metadata reconciliation found no resource attributable to this task.
No service, deployment, token, variable, or test secret was subsequently created. The projectCreate mutation has not been retried.
These client-side observations do not prove that the original mutation never committed. This request is not asking whether it is safe to retry.
If Railway staff require the workspace identifier for internal correlation, please specify a safe way to provide it without posting it publicly.
Please inspect provider-side records and confirm whether this specific mutation ever committed a project, including one subsequently deleted. If it committed, please provide the project ID and commit/creation timestamp. If it never committed, please identify the server-side evidence supporting that conclusion. If correlation or log retention prevents determination, please explicitly report that the outcome cannot be established.
3 Replies
6 hours ago
Your workspace has 0 active projects, and the only deleted projects in our records are four from August 2026, none of which match the name "guixu-cloudbook-g09-validation-v1-001". The projectCreate mutation that returned GRAPHQL_ERROR did not commit a project.
Status changed to Awaiting User Response Railway • about 6 hours ago
6 hours ago
Thanks. I want to distinguish an internal provider-side transaction conclusion from the same resource-list reconciliation already performed client-side.
Can you please confirm whether the statement that the mutation “did not commit a project” is based on provider-side mutation/transaction logs or other internal server-side records for this specific operation/time window, rather than being inferred only from the absence of an active or matching deleted project?
If Railway does not retain enough internal correlation data to establish that distinction, please explicitly state that the original mutation outcome cannot be determined.
Status changed to Awaiting Railway Response Railway • about 6 hours ago
6 hours ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 6 hours ago
6 hours ago
No me da