Cloud Functions: Function execution took 60000 ms, finished with status: timeout Google Cloud / Firebase Origin: Platform & cloud Last updated 4 Nov 2026

Cloud Functions: Function execution took 60002 ms, finished with status: 'timeout'

The function ran past its timeout (default 60s for HTTP 1st gen) and was terminated.

Exact message you may see Function execution took 60002 ms, finished with status: timeoutFunction execution took ms, finished with status: 'timeout'finished with status: 'error' Cloud FunctionsFunction execution took ms finished with status: 'crash'
Seen on: Google Cloud

Meaning

Increase --timeout (up to 9 min for 1st gen event functions; 60 min for 2nd gen HTTP) or make the work shorter/asynchronous. Check for unresolved promises, missing return/await, and slow downstream calls. For event-driven functions retries may re-run the function.

Common causes

  • Slow external call or database query
  • Promise never resolves / missing await
  • Heavy work done synchronously
  • Cold start plus long initialisation
  • Default timeout too low

⚡ Quick fix

  1. gcloud functions deploy FN --timeout=300s
  2. Fix async handling (await/return)
  3. Offload long work to Cloud Tasks / Cloud Run jobs

Detailed fix by platform

gcloud

  1. gcloud functions deploy FN --timeout=300s --region REGION

How to diagnose

  1. Duration — Time vs timeout?
  2. Async — Promises awaited?
  3. Dependencies — Slow calls?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Platform & cloud. Errors that are often confused with or caused by this one (click to open):

API has not been used in project before or it is disabled — Google Cloud: 403 SERVICE_DISABLED — Cloud Resource Manager API has not been used in project 123456 before or it is disabled. Enable it by visiting (Google Cloud / Firebase)API has not been used…Cloud Functions: Build failed — Cloud Functions: Build failed: function.js does not exist / npm install failed with exit code 1 (Cloud Build step) (Google Cloud / Firebase)Cloud Functions: Buil…Cloud Functions: Function failed on loading user code — Cloud Functions: Provided module can't be loaded / Function failed on loading user code. This is likely due to a bug in the user code (Google Cloud / Firebase)Cloud Functions: Func…Cloud Run 504: The request has been terminated because it has reached the maximum request timeout — Cloud Run: 504 Gateway Timeout — The request has been terminated because it has reached the maximum request timeout (Google Cloud / Firebase)Cloud Run 504: The re…context deadline exceeded — Go: Get "https://api.example.com": context deadline exceeded (Client.Timeout exceeded while awaiting headers) (Go)context deadline exce…Pub/Sub: messages redelivered (ack deadline exceeded) — Pub/Sub: Messages keep being redelivered — acknowledgement deadline expired before the subscriber acked (Google Cloud / Firebase)Pub/Sub: messages red…Your active project does not match the quota project in your local ADC — gcloud/ADC: WARNING: Your active project does not match the quota project in your local Application Default Credentials file (Google Cloud / Firebase)Your active project d…Cloud Fun…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.