From 4998a137ecea9d0062edbecca10565cecffb5315 Mon Sep 17 00:00:00 2001 From: "claude[bot]" <209825114+claude[bot]@users.noreply.github.com> Date: Wed, 23 Sep 2026 21:43:43 +0100 Subject: [PATCH] docs: correct function-to-function call rate limit for Edge Functions (#50806) Co-authored-by: Claude Co-authored-by: Kalleby Santos <105971119+kallebysantos@users.noreply.github.com> --- apps/docs/content/guides/functions/limits.mdx | 2 +- .../content/guides/functions/recursive-functions.mdx | 10 ++++++++-- 2 files changed, 9 insertions(+), 3 deletions(-) diff --git a/apps/docs/content/guides/functions/limits.mdx b/apps/docs/content/guides/functions/limits.mdx index 4ca38496c19..1280d17302c 100644 --- a/apps/docs/content/guides/functions/limits.mdx +++ b/apps/docs/content/guides/functions/limits.mdx @@ -25,7 +25,7 @@ subtitle: "Limits applied Edge Functions in Supabase's hosted platform." - Enterprise: Unlimited - Maximum log message length: 10,000 characters - Log event threshold: 100 events per 10 seconds -- Recursive/Nested Function Calling: ~5000 requests per minute [more details](/docs/guides/functions/recursive-functions) +- Recursive/Nested Function Calling: 30 requests per trace, within a 60-second window [more details](/docs/guides/functions/recursive-functions) ### Secrets diff --git a/apps/docs/content/guides/functions/recursive-functions.mdx b/apps/docs/content/guides/functions/recursive-functions.mdx index d661924efd1..8f73e89ed02 100644 --- a/apps/docs/content/guides/functions/recursive-functions.mdx +++ b/apps/docs/content/guides/functions/recursive-functions.mdx @@ -24,9 +24,15 @@ Inbound requests to your Edge Functions and requests to external APIs (e.g., Str ## Rate limit budget -Each request chain has a budget of at least **5,000 requests per minute**. In busier regions, this budget may be higher. All function-to-function calls within the same request chain share this budget. +Each request chain (or _trace_) has a budget of **30 requests within a 60-second window**. All function-to-function calls that share the same trace count toward this budget. -For example, if Function A calls Function B, and Function B calls Function C, all three calls count toward the same budget pool. +For example, if Function A calls Function B, and Function B calls Function C, all three calls count toward the same 30-request budget. + + + +A trace is the chain of calls that starts when one Edge Function invokes another. The budget applies per trace, not per project, so two separate invocations of the same function each get their own budget. + + ## Handling rate limit errors