Cloud Run request failed because the response was malformed or the instance connection failed
HTTP 503 The request failed because either the HTTP response was malformed or connection to the instance had an error.
Cloud Run returned a 503 because it could not communicate cleanly with the container instance, or because the response emitted by the app was malformed.
HTTP 503 The request failed because either the HTTP response was malformed or connection to the instance had an errorruntime
Observed message
HTTP 503 The request failed because either the HTTP response was malformed or connection to the instance had an error.
Why it happens
The container instance was unhealthy or terminated unexpectedly.
The app emitted a malformed HTTP response.
Memory pressure, liveness-probe failures, or framework timeouts interrupted the request before completion.
How to fix it
Inspect Cloud Logging for out-of-memory events, probe failures, and request-timeout behavior around the 503 responses.
Verify that the application is returning a valid HTTP response and not closing the connection unexpectedly.
If requests are timing out before Cloud Run's configured timeout, review the language framework's own timeout settings and health-check configuration.
