404 on deployed Edge Function despite successful deployment
Hey Supabase team 👋
I'm having trouble with my Edge Function used to send emails after a booking is completed.
The function deploys successfully, but when I invoke it, it returns a 404 (FunctionsHttpError). Details:
- Function name: sendBookingEmails
- Project ID: voyivdntptlofmxpwkis
- Function URL: https://voyivdntptlofmxpwkis.supabase.co/functions/v1/sendBookingEmails
- Deployment status: Successful (visible in the dashboard)
- Error: FunctionsHttpError (404)
- Context: The function should trigger the Resend API to send confirmation emails to both the client and the caregiver when a booking is confirmed.
- Plan: Free plan
I’ve confirmed that the function appears under Edge Functions in the dashboard and is deployed successfully.
It works locally, but when invoked from the frontend (via
Is there any configuration or authentication setting that could cause this issue?
Any help would be greatly appreciated 🙏
I'm having trouble with my Edge Function used to send emails after a booking is completed.
The function deploys successfully, but when I invoke it, it returns a 404 (FunctionsHttpError). Details:
- Function name: sendBookingEmails
- Project ID: voyivdntptlofmxpwkis
- Function URL: https://voyivdntptlofmxpwkis.supabase.co/functions/v1/sendBookingEmails
- Deployment status: Successful (visible in the dashboard)
- Error: FunctionsHttpError (404)
- Context: The function should trigger the Resend API to send confirmation emails to both the client and the caregiver when a booking is confirmed.
- Plan: Free plan
I’ve confirmed that the function appears under Edge Functions in the dashboard and is deployed successfully.
It works locally, but when invoked from the frontend (via
supabase.functions.invoke()), it returns a 404 error.Is there any configuration or authentication setting that could cause this issue?
Any help would be greatly appreciated 🙏
1 Reply
Could you share 1. The frontend code that you are invoking and 2. Are there any logs when you invoke the function i.e is the error after the function starts or after you invoke it but before it starts?
The only thing i can think off for edge functons is if
jwt_verify is set to true in under details in edge functions you are verifying with the legacy jwt secret
but some logs/ code snippets might clear things up more