2 months ago
I linked the development environment but our production is the most impacted
Attachments
3 Replies
2 months ago
The "failed to fetch snapshot" errors you're seeing are a transient build infrastructure issue on our side. We're aware of these issues and are actively working on improvements. Your production MAPI service's latest deployment did succeed, but the MAPI development service is still in a FAILED state in your development and staging environments. We'd recommend cancelling any queued builds and retrying the deployment once the issue clears, as additional redeploys can compound the queue.
Status changed to Awaiting User Response Railway • 2 months ago
Railway
The "failed to fetch snapshot" errors you're seeing are a transient build infrastructure issue on our side. We're aware of these issues and are actively working on improvements. Your production MAPI service's latest deployment did succeed, but the MAPI development service is still in a FAILED state in your development and staging environments. We'd recommend cancelling any queued builds and retrying the deployment once the issue clears, as additional redeploys can compound the queue.
2 months ago
response time is very high and service is returning 502 in some endpoints. Not all of them but some of them.
Attachments
Status changed to Awaiting Railway Response Railway • 2 months ago
2 months ago
This thread has been opened as a public bounty so the community can help solve it. The thread and any further activity are now visible to everyone.
Status changed to Open Railway • 2 months ago
2 months ago
Also, load average and CPU metrics differ...
Attachments