Skip to contentSkip to navigationSkip to topbar
Page toolsOn this pageProducts used
Looking for more inspiration?Visit the

80906: Interaction Not Open


WARNING: 80906

warning-80906 page anchor
FLEX
WARNING

This warning appears when Flex receives an interaction completion event for an Interaction that is already complete. In Flex Conversations, Interactions API operations trigger state change events, and a channel status can be active or closed, so a second completion after the channel is closed is logged as this warning.

Possible causes

possible-causes page anchor
  • Your application, webhook handler, Studio Flow, or backend job processed the same completion logic more than once for the same Interaction. This is the most likely cause when a duplicate completion reaches an Interaction after it has already moved to closed.
  • The Interaction Channel was already closed through the Channels subresource. Closing the channel also closes the underlying media channel and changes it to read-only.
  • Your workflow intended to remove the agent and keep the customer conversation available, but it closed the Interaction Channel instead. If you close the channel instead of updating the participant, later automation can still try to complete the same Interaction again.
  • Multiple automation paths handled terminal events without checking the current state first. Flex recommends handling terminal TaskRouter events such as workflow.timeout, task.canceled, and task.deleted according to your application's needs.
  • Check the current Interaction Channel status before you send completion or close logic. Only complete the Interaction when the channel is still active.
  • Make your completion handling idempotent. Deduplicate webhook retries and repeated automation so the same Interaction is not completed twice.
  • If you want to remove the agent but keep the conversation available for future activity, update the Channel Participant status to closed instead of closing the Interaction Channel. That completes the agent task while the channel remains active.
  • Review Interactions webhooks, Studio execution logs, TaskRouter events, and the Twilio Console debugger to identify which step closed the Interaction first.

Additional resources

additional-resources page anchor