-
-
Notifications
You must be signed in to change notification settings - Fork 12.6k
404 on edge function that clearly exists #35426
Copy link
Copy link
Closed
Labels
awaiting-detailsFor issues needing detail from the opener.For issues needing detail from the opener.bugSomething isn't workingSomething isn't workingexternal-issueCreated outside of SupabaseCreated outside of Supabase
Metadata
Metadata
Assignees
Labels
awaiting-detailsFor issues needing detail from the opener.For issues needing detail from the opener.bugSomething isn't workingSomething isn't workingexternal-issueCreated outside of SupabaseCreated outside of Supabase
Type
Fields
Give feedbackNo fields configured for issues without a type.
Bug report
Describe the bug
I've been running into an issue that happens quite frequently, and it seems to happen right after I deploy the (or any) edge function.
When I make a request to an edge function right after I deployed my edge function successfully, I get a 404. I know the edge function exists because I even tried to make a Test call to the edge function right from the dashboard, and it still gives a 404 (see screenshot).
The error seems to go away after I deploy again. But this really affects production and I would like to solve this.
I have a github action that successfully runs and deploys all edge function on merge or push or PR into main. The 404 error I described above seems to happen esp when I merge into main from another branch, but when I push directly into main, it seems to be fine. But the thing is the github action is always successful, and I can confirm this on the Supabase dashboard where I see my edge functions have been deployed. I'm saying, despite this, I get the 404 until direct push again (and therefore redployment).
Expected behavior
No 404s
Screenshots
[
](url)
System information