How I Fixed a Silent 500 Error in My Supabase Edge Function
How I Fixed a 500 Error That Was Silently Killing My SaaS I launched Torziva — an AI virtual try-on tool for fashion stores — and users were getting 500 errors on every try-on attempt. The weird pa...
Source: DEV Community
How I Fixed a 500 Error That Was Silently Killing My SaaS I launched Torziva — an AI virtual try-on tool for fashion stores — and users were getting 500 errors on every try-on attempt. The weird part? Supabase logs showed nothing. Completely blank. The Symptom Browser console: Failed to load resource: 500 Supabase edge function logs: blank fal.ai dashboard: requests weren't even arriving Classic "where is the request dying?" mystery. The Investigation Step 1 — Checked Vercel env vars My edge function was hosted on Supabase but the request originated from Vercel. Turned out FAL_API_KEY was missing from Supabase secrets — it was only in Vercel. Added it to Supabase → still failing. Step 2 — Checked the actual error Added more granular try/catch logging and finally saw it: Error: Processing timeout. Please try again. Step 3 — Found the real culprit My polling loop was set to 60 attempts × 2000ms = 120 seconds. Supabase edge functions have a default timeout of 60 seconds. The function was