Studio Flow Execution Failures Caused by Existing Active Conversations – Twilio Support

Issue

Studio flows fail to trigger for specific phone numbers because the user is already an active participant in an existing conversation. Customers often do not know which conversation SID the user is currently bound to.

Product

Twilio Conversations Classic

Environment

Twilio Console

Cause

When an inbound message or call arrives from a phone number that is already engaged in an active Twilio Conversation, Twilio routes the interaction to that existing conversation instead of executing the linked Studio flow.

Resolution

Find the active conversation associated with the participant's address and close it:

Query the ParticipantConversations resource using curl to list all conversations associated with the participant's URL-encoded phone number or address:

curl -X GET "https://conversations.twilio.com/v1/ParticipantConversations?Address=%2B1234567890&PageSize=20" \
-u $TWILIO_ACCOUNT_SID:$TWILIO_AUTH_TOKEN

Locate the active ConversationSid (CHXXXXXXXX...) from the API response payload.
Send a POST request to update the conversation state to closed:

curl -X POST "https://conversations.twilio.com/v1/Conversations/CHXXXXXXXX..." \
--data-urlencode "State=closed" \
-u $TWILIO_ACCOUNT_SID:$TWILIO_AUTH_TOKEN

Place a test interaction to confirm the Studio flow triggers as expected.

Additional Information

For detailed parameter usage and API specifications, refer to the Participant Conversation Resource documentation and the Updating a Conversation Resource guide.