2 months ago
We are experiencing persistent "Problem processing request" errors from the environmentLogs GraphQL endpoint across all environments (prod, staging, integration). The issue affects every log query regardless of filter, batch size, or direction.
Any environmentLogs query - even the simplest possible one with no filter and a limit of 10 - returns:
{"errors": [{"message": "Problem processing request", "traceId": "..."}]}
This started around 2026-03-12 5:00 AM UTC. Our API key and environment IDs have not changed. The issue is blocking all log ingestion pipelines.
Example traceId: 7141449999036631355
6 Replies
Status changed to Awaiting Railway Response Railway • 2 months ago
2 months ago
We're aware of an intermittent issue affecting log retrieval that can cause "Problem processing request" errors on the environmentLogs endpoint. This is a known platform-side issue we're tracking. If you're still seeing this, please let us know and we can follow up.
Status changed to Awaiting User Response Railway • 2 months ago
sam-a
We're aware of an intermittent issue affecting log retrieval that can cause "Problem processing request" errors on the environmentLogs endpoint. This is a known platform-side issue we're tracking. If you're still seeing this, please let us know and we can follow up.
2 months ago
Unfortunately, still seeing this issue in all environments we have
2 months ago
Hello, we've called an incident regarding the logs issue here https://status.railway.com/cmmp1u3tc0ai82tn1vdpm7mwj
Please stay tuned for updates, we're investigating the issue
2 months ago
Our incident regarding this has been updated https://status.railway.com/cmmp1u3tc0ai82tn1vdpm7mwj: we've confirmed logs are loading with elevated delay. Our team is aware and working on a fix.
2 months ago
We've implemented a fix and the logs should be returning to nominal soon, we're still monitoring
2 months ago
The logs incident has just been resolved https://status.railway.com/cmmp1u3tc0ai82tn1vdpm7mwj, please let us know if you're still running into this but logs should be back to normal now