[Question] Non-streaming response wall clock timeout?

In the case of the non-streaming response, would a long running langchain chain run until completion? Say a 20 minute chain? I am aware usage is based on CPU Time and not wall time, but curious if there's a timeout at all. Th

is would be a differentiating factor from others, for example, supabase edge functions iirc have a wall timeout of 1 minute, but is configurable if self hosting.

If Vercel is offering edge functions with CPU Time pricing _and_ no limit on wall clock time, then this would be KILLER for openai use cases even more than people think, since it would be perfect for such long chains that don't require streaming - aka post processing using langchain chains and only paying for CPU time.

@jaredpalmer

The issue mentions non-streaming LangChain chains running in Vercel Edge Functions with Next.js. Start by examining the repository's request path and the relevant Vercel Edge Function runtime limits, then verify whether a long-running non-streaming chain has a wall-clock timeout. Done means the behavior and applicable limits are clearly documented or confirmed.

Written by the indexing model from the issue text.