Thanks — that helps. Since the interruption happened when the caller interrupted your agent, this log means the system tried to resume a segment synchronizer after it had already been closed (an operation on a shut-down component). That usually happens when call lifecycle events overlap — e.g., interruption triggers closing or teardown of media/track components while another piece of code later attempts to resume them.
To narrow the root cause and give precise next steps, please tell me:
• Platform (iOS, Android, Web)
• LiveKit SDK version
• How the interruption is delivered (CallKit, Android telephony, custom signaling)
• Exact moment it appears (during ringing, active call, while agent publishes/plays audio, when app backgrounded, etc.)
• Any logs immediately before/after the message (2–5 lines)
With those details I can suggest targeted fixes (order-of-operations safeguards, checking closed state before resume, or lifecycle hooks to delay resume) and example checks you can add.