5 months ago
Hi Railway support,
I'm seeing a server-side error calling the Public GraphQL endpoint that affects the projects query. Details and reproduction steps below.
What I ran:
Verify token (works): curl -sS -X POST https://backboard.railway.com/graphql/v2
-H "Authorization: Bearer $RAILWAY_API_TOKEN"
-H "Content-Type: application/json"
-d '{"query":"query { me { id email } }"}'
Response: {"data":{"me":{"id":"a064355f-6b14-4e46-9527-15b6784a6c4f","email":"jfraserhhrock@gmail.com"}}}
Attempt to list projects (fails): curl -v -X POST https://backboard.railway.com/graphql/v2
-H "Authorization: Bearer $RAILWAY_API_TOKEN"
-H "Content-Type: application/json"
--data-binary '{"query":"query { projects { nodes { id name } } }"}'
Observed server response (full headers/body returned from curl):
HTTP status: 400
Date: Sat, 27 Sep 2025 14:17:36 GMT
CF-RAY: 985ba01d2fe6879a-IAD
Response body: {"errors":[{"message":"Problem processing request","traceId":"2730202379063267855"}]}
Other context
Earlier malformed PowerShell attempts produced JSON parse errors client-side; those were fixed and are unrelated now.
The token is confirmed valid for
me(so the token type/scopes appear correct).
Request
Please look up backend logs for traceId 2730202379063267855 (and CF-RAY 985ba01d2fe6879a-IAD at ~2025-09-27 14:17:36 UTC) and advise whether this is a resolver exception, permission issue, or WAF/gateway problem. If resolver exception, please share the internal error/stack trace or next steps we should take.
Thanks — let me know if you need additional curl traces or timestamps.
Pinned Solution
5 months ago
Hey!
Looks like your request is just a little mixed up. Below I've attached the correct GraphQL body.
query me {
me {
workspaces {
projects {
edges {
node {
id
name
}
}
}
}
}
}Let me know if this works!
3 Replies
5 months ago
Hey there! We've found the following might help you get unblocked faster:
If you find the answer from one of these, please let us know by solving the thread!
5 months ago
# Railway GraphQL `projects` escalation (redacted)
This file is a drafted escalation payload for Railway support. It intentionally does NOT include any secrets or tokens. Do NOT commit any files that contain secrets (e.g. `railway_variables.json`).
---
Subject: GraphQL `projects` query failing — please lookup traceId(s) and advise
Summary:
- Public GraphQL endpoint: https://backboard.railway.com/graphql/v2
- Token: Account-level PAT used (not included here).
- `me` query: succeeds and returns account id/email (token validated).
- `projects` query: returns server-side error.
Latest failing call (do not share token):
- When: 2025-09-27 ~14:17:36 UTC
- Request body: `{"query":"query { projects { nodes { id name } } }"}`
- Response body: `{"errors":[{"message":"Problem processing request","traceId":"2730202379063267855"}]}`
- CF-RAY: 985ba01d2fe6879a-IAD
Earlier traces collected (for correlation):
- traceId 5564792971008217649 (CF-RAY 985b8c0a1fab879a-IAD)
- reqId 9434e8c0-57f7-4fd2-9007-ce42ea575313 (client-side JSON parse during PowerShell quoting)
- traceId 5381837283146782772 (earlier `me` Not Authorized during initial tests)
What I can attach (do NOT include tokens):
- `curl -v` transcripts showing request/response headers (tokens redacted client-side before attaching)
- `--trace-ascii` output showing exact request bytes
- `smoke_out` artifact (deployed smoke) if support requests it
Request to Railway Support:
Please look up backend logs for traceId `2730202379063267855` (and the other traceIds above) and advise:
- Is this a resolver exception, gateway/WAF rejection, or permission issue?
- If a permission issue, what token type/scopes are required to call `projects` from the Public API?
- Any recommended workarounds while this is investigated.
Notes for internal use:
- I will attach transcripts but will NOT paste tokens. If Railway needs the token to reproduce, I can share it via a secure channel on request.
- Local file containing tokens: `railway_variables.json` (DO NOT commit to the repo). Move to an example file or add to `.gitignore` if needed.
request it via Railway's secure channel.
If you need the PAT, please request it via Railway's secure channel.
Attachments
5 months ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open brody • 5 months ago
5 months ago
Hey!
Looks like your request is just a little mixed up. Below I've attached the correct GraphQL body.
query me {
me {
workspaces {
projects {
edges {
node {
id
name
}
}
}
}
}
}Let me know if this works!
Status changed to Solved noahd • 5 months ago