2 months ago
Hello Railway team,
I am experiencing an unusual issue with my application deployed on your platform. When executing an action through a button, most of the time the data is saved correctly, but occasionally (around 5 out of 100 times) the data is not saved.
I have reviewed the logic in my code and it works properly, so I suspect the problem might be related to the infrastructure or database on Railway.
Could you please help me check if there might be intermittent connection issues, database configuration problems, or resource limitations that could be causing this inconsistency?
Thank you in advance for your support.
2 Replies
Status changed to Awaiting Railway Response Railway • 2 months ago
2 months ago
Hi there, I'm going to share this with our community to help you out and put a bounty of $20 on this question.
Your logs are showing connection pool churn which could mean an app-level connection management issue here. Our top bounty hunters and the community might be able to help debug your connection pooling and error handling.
Status changed to Awaiting User Response Railway • 2 months ago
2 months ago
Since your logs show "connection pool churn", it means that your application is opening, closing, or dropping database connections rather than reusing them. This is usually resolved by using a global, single instance of your database client in the code, or by utilizing a connection pooler on the database side. Ensure your database client (like PrismaClient) is instantiated globally and reused across all requests.
Check your database stats and see if Connections are maxed out, to verify this is the case.
Attachments