Netlify Function Timeout (502 / 504)

How to fix it

Try these in order — the most common fix is first.

1. 1. Use a background function

   Copy steps
   1. Name the file with the -background suffix; it runs up to 15 minutes but returns 202 immediately
   2. Store results in a database or blob store and poll
   Did this fix it? Yes No

2. 2. Stream large responses

   1. Return a streamed response (up to 20 MB)
   Did this fix it? Yes No

3. 3. Speed up the work

   1. Parallelize upstream calls, cache results, add timeouts to fetch
   Did this fix it? Yes No

4. 4. Use a scheduled function for cron work

   1. Scheduled functions allow 30 seconds
   Did this fix it? Yes No

5. 5. Raise memory/vCPU on Pro

   1. Set memory up to 4096 MB in config on credit-based Pro (cost scales)
   Did this fix it? Yes No

6. 6. Check logs

   1. Open Logs > Functions to see the failing invocation
   Did this fix it? Yes No

Symptoms

Requests return 502/504 or 'Task timed out' after about a minute, or large responses fail.

Why it happens

• Work exceeds the 60-second synchronous limit
• Payload above 6 MB buffered / 4.5 MB binary
• Slow upstream API
• Cold start plus heavy work
• Proxied requests time out after 26 seconds

This guide also covers

• netlify function timeout
• netlify function 502
• netlify task timed out
• netlify function 10 seconds

The same problem in other apps

All not loading, error messages & connection guides →

• Vercel FUNCTION_INVOCATION_TIMEOUT (504) Error (Vercel)

Other Netlify errors

• Netlify Page Not Found on Refresh (SPA 404)
• Netlify Build Failed
• Netlify Deploy Stuck on Building or Enqueued
• Netlify Custom Domain Not Working
• Netlify SSL Certificate Pending or Not Provisioning
• Netlify Site Paused: Credit Limit Reached
• Netlify Build Failed: Secrets Scanning Detected Secrets
• Netlify Environment Variables Undefined