Source code
Releases
Stability
Health endpoint behind auth / misleading
Part of the Production readiness check · fix arrives as a guide
What it is
The health endpoint sits behind authentication, or reports healthy based on something that does not reflect the service's ability to serve requests.
Why it matters
The platform's probe cannot authenticate, so it reads the 401 as a failure and restarts a healthy instance — or the check passes on a broken one and traffic keeps arriving.
How to fix it
Expose the probe endpoint unauthenticated but keep it free of any diagnostic detail, and have it assert what actually matters: that dependencies are reachable and the process can serve.
Run them all on your app
Connect your repo and your live services with read-only scopes. The first scan is free, and nothing changes without your approval.