/dependecies Endpoint Not Returning 200 After Database Recovery

[poojareddy0328]

We deployed our pactbroker on Openshift. To monitor our application's health, we included /heartbeat endpoint in our health checks. As /heartbeat endpoint doesn't report the database health, we tried to use /dependencies endpoint in our readiness probe to monitor the service's status and marks the container unready. However, even after database becomes available again, the /dependencies endpoint continues to return 500 and the issue resolves only after a manual restart of the pods.

We are looking for a solution to handle this gracefully, ensuring the service recovers automatically without requiring a manual pod restart. Any suggestions or best practices to address this issue would highly appreciated.