Repository navigation
🐞 Database connection does not retry after server restart #340
Description
Activity
Internal Server Error every time on server maintenance, please push the DB connection retry update
@rahulkumarsingh73690 Is this bug still open? Can I contribute?
@sutharjigar It’s still open; however, I am not sure if maintainers allow it because there is already 1 pr pending by @Razano26
So should I contribute (or give time to this or not)? @rahulkumarsingh73690
Hey! I set up the project locally and tested the DB restart scenario.
From my testing and reviewing the implementation, it looks like retry logic is already handled at the Prisma query level along with job-level retries.
The system successfully recovers after DB restarts, so this issue seems to be effectively resolved.
Let me know if any further improvements are expected here!
What happened?
When the database server restarts (or there’s a temporary DB outage), the app fails to reconnect automatically. It remains disconnected until the entire usesend app is manually restarted.
Expected behavior
The application should automatically retry the database connection and recover once the database is available again, without requiring a full app restart.
Actual behavior
The app stays disconnected and does not retry connecting to the database until the app is manually restarted.
Environment
Additional context
This can cause downtime in production if the database restarts due to maintenance, scaling, or temporary failures. A retry/backoff mechanism or persistent connection handling would improve reliability.
Replication Steps
Self hosted or Cloud?
Self hosted
What browsers are you seeing the problem on?
No response