Question: Extending Edge Function Timeout for Long-Running Tasks?
Hi everyone,
I have a question about Edge Function timeout limits. Is it possible to have them extended?
I'm currently trying to analyze very long meeting transcripts using Gemini. The issue I'm encountering is that even when the configured timeout for the Edge Function is hit (and the cron job invoking it reports a timeout error), the Edge Function itself often continues to run for about 3 minutes before it eventually shuts down.
Depending on Gemini's response speed, sometimes the analysis results are successfully saved back to Supabase. However, other times, the function shuts down before the process can complete, and the results are lost.
Is there any way to further increase the execution timeout for Edge Functions, or are there any best practices for handling such long-running tasks that might exceed the current limits?
Thanks!
I have a question about Edge Function timeout limits. Is it possible to have them extended?
I'm currently trying to analyze very long meeting transcripts using Gemini. The issue I'm encountering is that even when the configured timeout for the Edge Function is hit (and the cron job invoking it reports a timeout error), the Edge Function itself often continues to run for about 3 minutes before it eventually shuts down.
Depending on Gemini's response speed, sometimes the analysis results are successfully saved back to Supabase. However, other times, the function shuts down before the process can complete, and the results are lost.
Is there any way to further increase the execution timeout for Edge Functions, or are there any best practices for handling such long-running tasks that might exceed the current limits?
Thanks!
