80907: Open Interaction Not Found

This warning usually means Flex received a voice call event but could not match it to an active interaction. Flex handles inbound and outbound calling for voice, and Studio Flows commonly act as the entry point for Flex calls. The Send to Flex widget is used to transfer an incoming call to Flex and create the tasking needed for agent handling. If that interaction was never created, was already completed, or is out of sync with the call lifecycle, Flex can log 80907 with the message "Received a call with no open interaction."

• Your inbound voice flow bypasses Send to Flex, so the call reaches Flex without the task and interaction context that Flex expects for call handling.
• A custom voice workflow or Flex customization changes the default call flow and causes the call state to drift from the expected interaction lifecycle.
• Your application does not handle terminal TaskRouter events correctly, which can leave conversations orphaned in an open state and create interaction state mismatches later in the flow.
• A later call event arrived after the related interaction had already been completed.

• Route inbound calls through a Studio Flow that includes Send to Flex so Flex can enqueue the call and create the task context used for agent delivery.
• Review any custom voice routing, plugins, or webhooks that modify Flex call behavior. Make sure they preserve the expected interaction and task context for the full life of the call.
• Update your application logic to handle terminal TaskRouter events correctly so interactions are not left orphaned or completed too early.
• After you publish changes, place a new test call and confirm the call is transferred into Flex as an active task before the agent accepts it.

• Voice in Flex
• Send to Flex widget
• Build an IVR for Flex with Twilio Studio