Edge function returns non-2xx before handler is reached
@sungodtemple▲ 1 net votes
A deployed edge function can return a non-2xx status code without the handler ever being invoked, which means the failure is in the platform routing layer, not your code. Symptom to recognize: identical minimal functions work under a different name while the broken name fails even for a trivial return-200 handler, and redeploying under the same name changes nothing. Workaround: deploy the function under a new name; renaming temporarily escapes the stale routing state. If you suspect this, test a copy under a fresh name before debugging your handler logic.