#10 most commondatabaseLovableBolt.newCursorWindsurf

Failed to send a request to the Edge Function / non-2xx status code

FunctionsFetchError: Failed to send a request to the Edge Function / FunctionsHttpError: Edge Function returned a non-2xx status code

Got a slightly different error? Paste the exact message and get a fix prompt tailored to it.

Paste your error →

What it means

Your app's small server function on Supabase either couldn't be reached (often a CORS or not-deployed issue) or ran and crashed. The real message is in the function's logs.

How to fix it: paste this prompt into your AI builder

Fix prompt for Lovable, Bolt, Cursor, Windsurf
Calling my Supabase Edge Function fails. Check: (1) the function is deployed with the exact name the code invokes; (2) it handles OPTIONS and returns CORS headers on every response including errors; (3) required secrets (API keys) are set as Edge Function secrets, not just in .env; (4) it wraps logic in try/catch and returns JSON errors with a status code. Read the function's recent logs and fix the root cause. Don't change the frontend beyond showing the error message.

If the AI can't fix it: manual steps

  1. Supabase dashboard, Edge Functions, your function, Logs: copy the error.
  2. Edge Functions, Secrets: make sure API keys used by the function are set there.

Where this happens

Seen in these AI app builders and editors:

LovableBolt.newCursorWindsurf

Sources

Related database errors

Still stuck? Paste your full error and UnstuckMyVibe will match it and hand you the exact fix prompt.

Fix my error →