The Postgres development platform. Supabase gives you a dedicated Postgres database to build your web, mobile, and AI applications.
TypeScript aialternativeauthdatabasedenoembeddingsexamplefirebasenextjsoauth2pgvectorpostgispostgrespostgresqlpostgrestrealtimesupabasevectorswebsockets
fix(docs): Update Edge Function error code from WORKER_LIMIT to WORKER_RESOURCE_LIMIT (#46051)
Timothy Lim360140b3de31
diff --git a/apps/docs/content/guides/functions/status-codes.mdx b/apps/docs/content/guides/functions/status-codes.mdxindex 49e51ee9f5b..e10548aa25a 100644--- a/apps/docs/content/guides/functions/status-codes.mdx+++ b/apps/docs/content/guides/functions/status-codes.mdx@@ -109,7 +109,7 @@ You can see the output in the [Edge Function Logs](/docs/guides/functions/loggin### 546 Resource Limit (Custom Error Code)-**Cause:** Your Edge Function execution was stopped due to exceeding resource limits (`WORKER_LIMIT`). Edge Function logs should provide which [resource limit](/docs/guides/functions/limits) was exceeded.+**Cause:** Your Edge Function execution was stopped due to exceeding resource limits (`WORKER_RESOURCE_LIMIT`, previously it was `WORKER_LIMIT`). Edge Function logs should provide which [resource limit](/docs/guides/functions/limits) was exceeded.**Common causes:**diff --git a/apps/docs/content/troubleshooting/edge-function-546-error-response.mdx b/apps/docs/content/troubleshooting/edge-function-546-error-response.mdxindex cca513f9a48..5a632cc7455 100644--- a/apps/docs/content/troubleshooting/edge-function-546-error-response.mdx+++ b/apps/docs/content/troubleshooting/edge-function-546-error-response.mdx@@ -1,15 +1,19 @@----title = "546 - WORKER_LIMIT Exceeded"+title = "546 - WORKER_RESOURCE_LIMIT Exceeded / WORKER_LIMIT Exceeded"topics = [ "functions" ]keywords = [ "546", "error", "resource", "memory", "cpu", "event loop", "edge function" ]database_id = "4e6ff2e4-2abb-4fba-8233-5883b3d56fb0"+[[errors]]+http_status_code = 546+message = "WORKER_RESOURCE_LIMIT"+[[errors]]http_status_code = 546message = "WORKER_LIMIT"----A 546 error indicates that an edge function used more resources (CPU or Memory) than it was allocated.+A 546 error indicates that an edge function used more resources (CPU or Memory) than it was allocated. Previously it was `WORKER_LIMIT`.## Context for the error@@ -37,7 +41,7 @@ When an edge function fails due to internal CPU or memory limits, it will return```json{- "code": "WORKER_LIMIT",+ "code": "WORKER_RESOURCE_LIMIT","message": "Function failed due to not having enough compute resources (please check logs)"}```diff --git a/apps/docs/content/troubleshooting/http-status-codes.mdx b/apps/docs/content/troubleshooting/http-status-codes.mdxindex b81da31d103..299287c0dff 100644--- a/apps/docs/content/troubleshooting/http-status-codes.mdx+++ b/apps/docs/content/troubleshooting/http-status-codes.mdx@@ -70,4 +70,4 @@ The timeout limit is set to prevent long-running queries which can cause perform#### 546 Edge Functions resource limit-Applies only to Edge Functions. Function execution was stopped due to a resource limit (`WORKER_LIMIT`). Edge Function logs should provide which [resource limit](/docs/guides/functions/limits) was exceeded.+Applies only to Edge Functions. Function execution was stopped due to a resource limit (`WORKER_RESOURCE_LIMIT`). Edge Function logs should provide which [resource limit](/docs/guides/functions/limits) was exceeded.