50353: Conversation with provided unique name already exists

Twilio returns this error when your request tries to create a Conversation with a unique_name value that is already assigned to another Conversation in the same Conversations Service. Each Conversation unique_name must be unique within your service.

• Your application sends a unique_name that already exists on another Conversation
• A retry or duplicate request attempts to create the same Conversation more than once
• Multiple application workers or processes try to create a Conversation with the same unique_name at nearly the same time
• Your application reuses a static or predictable unique_name instead of generating a value that is unique for each Conversation

• Check whether a Conversation with the same unique_name already exists before you create a new one
• Update your application logic to generate a unique unique_name for each new Conversation
• If you need to reuse an existing conversation, fetch the existing Conversation by its identifier instead of creating a new one
• Add idempotency or request de-duplication in your application to prevent repeated create requests with the same unique_name
• If concurrent requests can create the same Conversation, add application-side locking or conflict handling so only one request creates the resource

• Conversations overview
• Conversations API