We are using Vercel WebSockets with maxDuration set to 1800 seconds (30 minutes). According to the documentation, connections close at the function's maximum duration, and reconnects may land on a different instance.

Consider long-running audio sessions such as online meetings or voice conversations: audio is received continuously, while processing may be triggered later for a specific time window. If a reconnect happens during that window, pending audio and session context held by the previous instance or an upstream real-time service may no longer be available to the new connection.

Could Vercel support WebSocket sessions lasting 2–3 hours to cover this basic use case?

If the current duration limit cannot be extended, is there a recommended, supported approach that preserves continuous audio ingestion and processing context across reconnects? Practical guidance or a minimal example would be helpful.

Documentation: https://vercel.com/docs/functions/configuring-functions/duration https://vercel.com/docs/functions/websockets