What happened
When the SMS gateway is intentionally unavailable, an authenticated request to the GSM health check returns HTTP 500. The main server logs an unhandled connection error and a full ASGI traceback, which makes normal server logs difficult for developers to inspect.
What I expected
An unavailable SMS gateway is an expected state. The health check should return a deliberate unavailable/degraded response and log the condition concisely, without an unhandled exception or traceback.
Steps to reproduce
- Start the main SAPOT server while the SMS gateway service is intentionally stopped or unreachable.
- Authenticate as a user.
- Request the GSM health check.
- Observe HTTP 500 and a full upstream connection traceback in the main-server logs.
Additional context
The gateway is expected to be unavailable in some deployments or during normal maintenance. The response should let clients and operators identify this expected dependency state while keeping server logs actionable.
What happened
When the SMS gateway is intentionally unavailable, an authenticated request to the GSM health check returns HTTP 500. The main server logs an unhandled connection error and a full ASGI traceback, which makes normal server logs difficult for developers to inspect.
What I expected
An unavailable SMS gateway is an expected state. The health check should return a deliberate unavailable/degraded response and log the condition concisely, without an unhandled exception or traceback.
Steps to reproduce
Additional context
The gateway is expected to be unavailable in some deployments or during normal maintenance. The response should let clients and operators identify this expected dependency state while keeping server logs actionable.