diff --git a/apps/docs/content/guides/functions/error-codes.mdx b/apps/docs/content/guides/functions/error-codes.mdx
index cd9e1a4bb5d..e6117c0592f 100644
--- a/apps/docs/content/guides/functions/error-codes.mdx
+++ b/apps/docs/content/guides/functions/error-codes.mdx
@@ -264,6 +264,21 @@ These errors indicate issues with function loading, execution, or the underlying
 
 **Solution:** Try redeploying your function and wait a few minutes to make sure all regions have been updated.
 
+### NOT_FOUND_FUNCTION_BLOB
+
+**Cause:** Your Edge Function metadata resolved, but its deployment bundle was missing from storage and could not be loaded (the metadata points at a different version than the stored bundle). This returns the same `Requested function was not found` message as `NOT_FOUND`, so the `sb-error-code` header is what distinguishes them — see [Edge Function 404 error response](/docs/guides/troubleshooting/edge-function-404-error-response).
+
+**Common causes:**
+
+- Two deploys of the same function running concurrently, double-incrementing the metadata version
+- A batch deploy using `/deploy?bundleOnly=true` where the bulk metadata update failed
+
+**Solution:**
+
+- Redeploy your function with the latest version of the Supabase CLI
+- Avoid running concurrent deploys of the same function, such as overlapping GitHub Actions runs
+- If the problem persists, contact support so your function metadata can be re-synced
+
 ### BOOT_ERROR
 
 **Cause:** Your Edge Function failed to start.
@@ -302,3 +317,12 @@ These errors indicate issues with function loading, execution, or the underlying
 
 - Try redeploying your function
 - If the problem persists, contact support
+
+### LOAD_FUNCTION_UNBUNDLING_ERROR
+
+**Cause:** Your Edge Function deployment bundle was fetched, but could not be unbundled because decompressing or parsing it failed. This usually means the bundle is corrupt or was only partially written.
+
+**Solution:**
+
+- Try redeploying your function
+- If the problem persists, contact support