serverpod-sessions

A "StateError: session already closed" occurs when a delayed callback like a timer captures a request-scoped session and runs after the endpoint returns. Refactor the delayed work into a future call or a fresh internal session.

Safely manage InternalSession lifecycle by creating and closing the session inside a finally block. This ensures reliable async cleanup and prevents leaked memory and logs if the long-running task throws an exception.

Use will-close cleanup listeners in Serverpod WebSocket handling to execute async cleanup callbacks correctly before the stream terminates. This prevents capturing request sessions for work that runs beyond the stream's lifetime.

The correct session lifetime for Serverpod future calls and web routes is strictly bound to the request or stream scope. Avoid capturing these request-scoped sessions for any background work that outlives the endpoint execution.

Prevent Serverpod session leaks by avoiding the capture of request-scoped sessions beyond the stream lifetime. Use addWillCloseListener correctly and ensure all async cleanup logic executes before the stream closes.

You only need to manually create and close InternalSession for longer-running work outside standard endpoint methods. Standard method calls, web routes, and streams handle request-scoped session lifetimes automatically upon return.