Error AtlasError Documentation and Resolution
Back to search

Cloud Run

Cloud Run request hit the HTTP 504 timeout

HTTP 504

Cloud Run terminated the request because it exceeded the configured request timeout before the container returned a complete response.

HTTP 504runtime

Observed message

HTTP 504

Why it happens

  • The request takes longer than the configured Cloud Run timeout.
  • The service is waiting on a slow dependency or blocking operation.
  • Long-running work is being handled synchronously in the request path.

How to fix it

  1. Reduce the amount of work performed during a single request.
  2. Move long-running work to background processing or asynchronous workflows.
  3. Increase the request timeout only when the workload genuinely requires it.

Official reference

Google Cloud: Troubleshoot Cloud Run issues

Related errors

While handling this request, the container instance was found to be using too much memory and was terminated.Cloud Run container instance was using too much memory and was terminatedHTTP 500 error codes in the logsCloud Run deployment succeeded but logs show HTTP 500 errorsHTTP 429 The request was aborted because there was no available instanceCloud Run request aborted because there was no available instanceHTTP 503 The request failed because either the HTTP response was malformed or connection to the instance had an errorCloud Run request failed because the response was malformed or the instance connection failed

Explore more

runtimeBrowse more runtime errors
Cloud Run HTTP 504 timeout: causes and fixes | Error Atlas