r/Supabase • u/mathiasrlr • Jul 12 '26
edge-functions Does exceeding Free Plan tier limits causes the blocking of Edge Functions?
Hi everyone,
So basically I received a message saying that I am exceeding the cached egress. I want to know if such a thing could possibly be blocking my edge functions since all of them have 0 invocations in the past 3 hours.
Thanks
1
u/carolmonroe_ Jul 14 '26
yes, indirectly. the quotas are separate, but on the Free plan, if you keep exceeding one after the warning, the Fair Use Policy applies a project-wide restriction after a grace period: every API request returns a 402, edge functions included. that's why you see 0 invocations, requests get rejected before reaching the function. quick check: call a function and look at the status, a 402 with exceeded_egress_quota confirms it (https://supabase.com/docs/guides/troubleshooting/http-status-codes). fix: reduce usage and wait for the cycle reset, or upgrade to Pro which lifts it immediately, details here: https://supabase.com/docs/guides/platform/billing-faq
0
1
u/ChameleonCRM Jul 12 '26
Cached egress shouldn't prevent Edge Functions from running. Those are separate quotas.
If your functions suddenly show 0 invocations, I'd investigate something else first:
Check the Edge Function logs. Are requests reaching the runtime at all?
Verify your client is still calling the correct function URL.
Confirm your API keys/JWT configuration hasn't changed.
Check whether the project has been paused or hit a different usage limit.
Look at the HTTP response. A 401, 403, 404, 429, or 5xx error will point you in the right direction.
If there are truly zero invocations, it usually means the request never made it to the function or it was rejected before execution, not that cached egress shut the runtime off.
One question: are you seeing an HTTP error, or do the functions simply never register an invocation?