Edge API route fails but returns a 404 response code
Unanswered
Anirudh posted this in #help-forum
AnirudhOP
I have an API route that fails with error INTERNAL_EDGE_FUNCTION_INVOCATION_FAILED, but instead of returning a 504 http status code in the response, it is sending a 404 instead. It also seems like whenever that error occurs, the _error path is also called. The original API route is defined in the App directory with edge runtime. Any idea what is happening here?
1 Reply
AnirudhOP