Feature: No clear and concise error messaging on UI in case postgres or NATS is down #5947
Description
🔖 Feature description
CASE : I
Implement a UI notification that clearly indicates when PostgreSQL is down. Currently, when PostgreSQL is unavailable, users receive a generic "Please login again" message, and the login API returns a 500 status code. The system should display a specific error indicating that PostgreSQL is down to improve transparency and facilitate troubleshooting.
CASE : II
Implement a clear UI notification or log message that indicates the cause when a CI build is stuck. Currently, when a CI build is stuck, there is no clear indication of the root cause. In this specific case, the build was halted because NATS was down, but this was not reflected in the system. A feature should be added to show specific errors, such as NATS is down, to help identify the issue and improve transparency during build failures.
🎤 Pitch / Usecases
CASE: I
When PostgreSQL is unavailable, display a specific error message on the UI (e.g., "PostgreSQL is currently down") to inform users about the root cause of login failures.
CASE: II
When NATS is down, provide a clear notification in the UI or CI logs (e.g., "NATS service is down") to explain why CI builds are stuck, improving visibility and troubleshooting.
🔄️ Alternative
No response
👀 Have you spent some time to check if this issue has been raised before?
- I checked and didn't find similar issue
🏢 Have you read the Code of Conduct?
- I have read the Code of Conduct