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.
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' 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
gcloud functions deploy FN --timeout=300s- Fix async handling (await/return)
- Offload long work to Cloud Tasks / Cloud Run jobs
Detailed fix by platform
gcloud
gcloud functions deploy FN --timeout=300s --region REGION
How to diagnose
- Duration — Time vs timeout?
- Async — Promises awaited?
- 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:
Similar errors
- 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
- Cloud Functions: Build failed Cloud Functions: Build failed: function.js does not exist / npm install failed with exit code 1 (Cloud Build step)
- 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
Most viewed in Google Cloud / Firebase
- Missing or insufficient permissions Firestore: FirebaseError: [code=permission-denied]: Missing or insufficient permissions
- Container failed to start Cloud Run: The user-provided container failed to start and listen on the port defined provided by the PORT=8080 environment variable
- Could not load the default credentials Google Cloud: Error: Could not load the default credentials. Browse to https://cloud.google.com/docs/authentication/getting-started
Other ways to find it
Where this error sits
Origin: Platform & cloud. Errors that are often confused with or caused by this one (click to open):
🧠 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.
Report a correction or suggest an improvement
Last updated 4 Nov 2026