From d101d6f3de4cb7bbace70cdd62fe2712bcfdc7fd Mon Sep 17 00:00:00 2001 From: Abhishek Tripathi <63142055+abhins0554@users.noreply.github.com> Date: Wed, 5 Aug 2026 21:41:00 +0530 Subject: [PATCH] docs: document NOT_FOUND_FUNCTION_BLOB Edge Function error (#48411) This PR addresses the documentation portion of #47739. ## What the issue means `NOT_FOUND_FUNCTION_BLOB` means the runtime cannot find the deployed bundle for an Edge Function. This differs from the existing `NOT_FOUND` error, which normally indicates that the function name in the request URL is not recognized. The dashboard status alone may not reveal this failure because the function can still appear as `ACTIVE`. ## Changes - Documented `NOT_FOUND_FUNCTION_BLOB` as an HTTP 404 error. - Explained how it differs from `NOT_FOUND`. - Added the command for redeploying one affected function. - Added the command for redeploying all functions when several are affected. - Added guidance to retry the request and contact Support if redeployment does not resolve the problem. ## Files changed - `apps/docs/content/troubleshooting/edge-function-404-error-response.mdx` ## Validation - The change uses the troubleshooting page's existing TOML frontmatter and MDX conventions. - `git diff --check` passes. ## Summary by CodeRabbit * **Documentation** * Expanded troubleshooting guidance for Edge Function 404 responses. * Added coverage of the `NOT_FOUND_FUNCTION_BLOB` error, including example responses and clarification of how it differs from `NOT_FOUND`. * Updated redeployment instructions with options for deploying a single function or all functions. * Refined retry and support guidance. --- .../edge-function-404-error-response.mdx | 30 ++++++++++++++++--- 1 file changed, 26 insertions(+), 4 deletions(-) diff --git a/apps/docs/content/troubleshooting/edge-function-404-error-response.mdx b/apps/docs/content/troubleshooting/edge-function-404-error-response.mdx index 19afdd4c4aa..c3016171c83 100644 --- a/apps/docs/content/troubleshooting/edge-function-404-error-response.mdx +++ b/apps/docs/content/troubleshooting/edge-function-404-error-response.mdx @@ -8,9 +8,14 @@ database_id = "a3cfff33-d640-4395-99bc-a110b7fb637c" http_status_code = 404 code = "NOT_FOUND" message = "Requested function was not found" + +[[errors]] +http_status_code = 404 +code = "NOT_FOUND_FUNCTION_BLOB" +message = "Function deployment bundle not found" --- -The edge function is not recognized by Supabase +The edge function is not recognized by Supabase, or its deployed bundle cannot be found. ## Context for the error @@ -51,6 +56,20 @@ When an edge function fails due to a platform 404 error, it will return the erro } ``` +A different platform 404 error, `NOT_FOUND_FUNCTION_BLOB`, can occur when the function name is recognized but the runtime cannot find the deployed bundle. This can happen even when the function appears as `ACTIVE` in the dashboard, because the status shows that the function record exists while the actual deployment bundle is missing or inaccessible: + +```json +{ + "code": "NOT_FOUND_FUNCTION_BLOB", + "message": "Function deployment bundle not found" +} +``` + +The difference between the two errors is: + +- `NOT_FOUND`: The function name in the request URL is not recognized. +- `NOT_FOUND_FUNCTION_BLOB`: The function name is recognized, but the runtime cannot find the deployed bundle. + ### Inspecting the logs @@ -99,20 +118,23 @@ If the call works, consider double checking your code for typos or to see if it ### Step 4: Redeploy the function -If step 3 fails, it may be a sign of an internal bug and it may be necessary to redeploy your function. This can be done within the [Function Dashboard](/dashboard/project/_/functions) under the respective function's code tab: +If step 3 fails, it may be a sign of an internal bug and it may be necessary to redeploy your function. The same applies if you see the `NOT_FOUND_FUNCTION_BLOB` error, which means the function is recognized but its deployed bundle cannot be found. This can occur even when the function appears as `ACTIVE` in the dashboard. + +This can be done within the [Function Dashboard](/dashboard/project/_/functions) under the respective function's code tab: ![image](/docs/img/troubleshooting/edge_function_404_redeploy.png) Alternatively, if you develop locally, you can redeploy the function with the [Supabase CLI](/docs/guides/local-development/cli/getting-started?queryGroups=platform&platform=macos): ```sh +# Redeploy one affected function supabase functions deploy FUNCTION_NAME -# If you want to deploy all functions, run the `deploy` command without specifying a function name: +# Or redeploy all functions if several are affected supabase functions deploy ``` -Then write in a ticket to [Supabase Support](/dashboard/support/new) +After redeploying, retry the request. If the error persists, write in a ticket to [Supabase Support](/dashboard/support/new). ## Additional resources