EdgeFunction processing stops at 200s.

[corosk]

According to the following document, the limit of Edge Function execution time is 400s for a paid plan, but when I run it in my environment, EdgeFunction processing stops after 200s.
Does anyone else have a similar problem?

https://supabase.com/docs/guides/functions/limits

I would like to know if there is a way to reduce it to 400s, because at 200s, the architecture itself using EdgeFunction needs to be rethought.

[GaryAustin1]

What are you doing and what are your errors?
The 150 and 400 second times are the max a function will hang around doing nothing basically. During that period it can run 1 or more invocations

But you only have 2seconds of CPU time and 150seconds of idle time per invocation.

Your last comment/question is unclear as you want to reduce to 400s?
You also don't say if you are Free or Pro.

[corosk]

Thank you for the clarification. I'm on the Pro Plan.
To clarify my question: I understand that the 400s limit refers to the maximum idle time before the function is terminated, not continuous CPU execution time. However, in my case, the Edge Function appears to be stopping after 200s even during active processing (not idle time).
My use case involves:

Document analysis using Gemini API
The process requires more than 200s of actual execution time
No specific error messages are thrown - the function simply shuts down after 200s

My question about "reducing to 400s" was poorly worded - I meant "extending to the full 400s limit" that should be available on the Pro Plan according to the documentation.
Has anyone experienced Edge Functions terminating before reaching the documented limits? Or are there specific configuration settings I might be missing to utilize the full 400s timeout on Pro Plan?
If the current architecture limitations make this unfeasible, I'll need to redesign the solution, but I want to make sure I'm not missing something first.

[GaryAustin1]

Each invocation is a max of 150s it appears even on pro. It is just that pro can run more invocations before the function terminates and has to be reloaded. Or at least that is how I read it.

[corosk]

Thank you for that insight. That interpretation makes sense - so even on Pro Plan, each individual invocation is still limited to 150s, but Pro allows for more invocations within the 400s total function lifetime.

Additional information: I checked other Edge Functions in my environment and found that all functions consistently shut down exactly at 200 seconds - from boot to shutdown. Even when the internal processing completes in less than 200s, the shutdown still occurs at exactly 200 seconds.
If the rule is 150s per invocation as you mentioned, do you know what accounts for this 50-second difference? Is there perhaps additional overhead time, or could there be a different timeout configuration in my setup?

[GaryAustin1]

Sorry, I don't. I actually don't find 200 mentioned at all in the source or issues, but I'm not an expert on edge functions.
You might want to generate an issue here: https://github.com/supabase/edge-runtime/issues
Also any change your endpoint you are calling is timing out at 200?

[zoltan-szalontai]

I also have issues with this on the pro plan. It is supposed to stream response from another HTTP API call but it just shuts down after 200 seconds and never processes whatever is streamed after that.

Looks like a bug because the documentation says 400 sec everywhere.

[GaryAustin1]

I don't know why the 200 seconds but 150 seconds is the max runtime per request. You can respond to the request before that and run in the background to 400 I believe. Otherwise the 400 is just how long the function code is alive to handle multiple calls less than 150seconds.
Or at least the is my understanding.

If you think that interpretation is in correct or need an answer to 200 verus 150 (or 400 if background) then please generate an issue in supabase/edge-runtime repository.

[zoltan-szalontai]

Yeah because I send the response after 10 sec so I think that idle timeout is not applicable here. WIll try an issue where you suggested, thanks for the reply.

[anik8das]

I'm also facing the same issue. Could someone find clarification of the timeouts?