---
"@context": https://schema.org
"@type": TechArticle
"@id": https://www.twilio.com/docs/api/errors/50391#article
headline: "50391: Conflicting conversation modification"
url: https://www.twilio.com/docs/api/errors/50391
inLanguage: en
dateModified: 2026-03-11T20:43:38.000Z
author:
  "@type": Organization
  name: Twilio Developer Education Team
publisher:
  "@type": Organization
  name: Twilio
---

# 50391: Conflicting conversation modification

Log Type: APPLICATION

Log Level: ERROR

## Description

The requested conversation is already being added or removed from this service instance concurrently with another API request. The last request will be rejected to avoid inconsistent state.

### Possible causes

* You might be adding a new conversation to the service instance while the conversation with the same unique name is being removed from another thread.
* You might be submitting multiple concurrent requests to add a conversation with the same unique name to the service instance.
* You might be submitting multiple concurrent requests to delete the same conversation by SID or unique name from the service instance.

### Possible solutions

* Implement an operation retrier and repeat the failed conversation API requests after an interval of time, using an exponential backoff algorithm.
* Review your application logic that caused the race condition when adding or removing users. Perhaps the conflicting operations are happening in a loop that could be avoided.
* Serialize your API requests that add or remove conversations. Wait until the original request completes and returns an API response, before sending any successive conversation requests.