Try or ByeTry or Bye

Supabase Edge Function 546 WORKER_LIMIT Error

Workaround available Edge Functions (Deno) Updated October 21, 2026

Quick answer

Error 546 means the function exceeded its CPU (2 s) or memory (250 MB) budget or wall-clock limit. Check function logs for which limit was hit and split or optimize the work.

Most likely fix: Find which limit was hit.

Symptoms

Function returns status 546 with WORKER_RESOURCE_LIMIT / WORKER_LIMIT, or logs show 'wall clock time limit reached'; separately, boot errors return 503.

Why it happens

  • CPU-heavy work (image processing, large JSON parsing)
  • Memory over 250 MB
  • Long external API calls exceeding wall-clock time
  • Boot error: syntax error, unsupported import or missing secret

How to fix it

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

  1. 1. Find which limit was hit

    1. Dashboard > Edge Functions > your function > Logs
    2. Look for memory or CPU-time messages; check the Metrics tab

  2. 2. Reproduce locally with debug

    1. Run supabase functions serve <name> --debug
    2. Check stack traces and unresolved promises

  3. 3. Split heavy work

    1. Process data in smaller chunks
    2. Move long jobs to a queue or background worker

  4. 4. Add timeouts to external calls

    1. Wrap fetch calls with AbortController timeouts

  5. 5. Fix boot errors

    1. Check that imports are Deno-compatible
    2. Set secrets with supabase secrets set before deploying

This guide also covers

  • supabase edge function 546
  • supabase worker_limit
  • supabase edge function error
  • supabase function invocation failed

Still not working?

If Supabase keeps failing, you're not alone. See every Supabase problem users report or the alternatives people switch to.

Other Supabase errors