80607: Session Closed

This warning appears when you attempt to update a Proxy Session whose status is already closed. You may see the message "Session is closed and cannot be updated." Proxy Sessions have a defined lifecycle, and updates are only valid while the Session is still active.

• Your application sent an update request to a Session after its status had already been set to closed.
• Your workflow closed the Session when the interaction was complete, then attempted another Session update later. In Proxy, a closed Session is no longer treated as an open Session for calls or messages.
• An inbound call or SMS arrived after the Session was closed, but your application still expected that Session to be updated or reused. Proxy handles this as out-of-session traffic instead.

• Check the Session status before sending an update request. Only update Sessions that are still active.
• Use valid Session status transitions in your workflow. To close a Session, update it from open to closed or from in-progress to closed.
• If the participants need to communicate again after a Session has been closed, create a new Session instead of trying to update the closed one. Proxy can also auto-create a new Session for out-of-session traffic when you return valid JSON from your out-of-session callback.
• Configure outOfSessionCallbackUrl on the Proxy Service to handle calls or SMS that arrive on a closed Session. You can return TwiML to respond to the interaction or return JSON to create a new Session.

• Session Resource
• Service Resource
• Out-of-Session Callback Response Guide