45301: Error occurred when connecting to a Meeting Participant

This error means Flex couldn't finish connecting another user as a meeting participant. Flex reports this error when it encounters a service error while connecting to a user. In practice, this can appear during live call workflows that require Flex to connect another participant, such as call monitoring or warm transfer.

• Flex encountered a service error while trying to connect the participant.
• The action was attempted in a workflow that depends on a live, conference-based call. For warm transfer, the call must be live, you can't already be in another transfer, and the action won't work while you're on hold.
• The user attempting the action wasn't allowed to monitor or join the target interaction. Admins can monitor calls, while supervisors who aren't team owners can't monitor call transactions.
• Team ownership or team membership changes weren't yet reflected in Flex UI. After a team owner change, refresh Flex UI. After moving a user to a team, that user must complete an activity in Flex UI before they appear correctly on the Teams page.

• Retry the action after confirming the interaction is still live and conference-based, and that you're not on hold or already in another transfer.
• If you're monitoring a call, make sure the acting user is an admin or owns the target agent's team. If you recently changed team ownership, refresh Flex UI before trying again.
• Open the Flex Status Report or download an error report to capture more detail about the failure. If the issue is part of a broader platform disruption, review the Twilio Status page.
• Review Flex error logs in Debugger and run System checkup in Console to identify runtime or configuration issues.

• Warm transfer
• Monitor agent activity
• User Guide to Troubleshooting the Flex UI