# 45796: Operation failed: conflict with current resource state

Log Type: APPLICATION

Log Level: WARNING

## Description

This warning indicates that Twilio could not complete the Flex operation because the target resource was in a conflicting state. This usually happens when another update reaches the same resource at about the same time, so your request no longer matches the resource's latest state.

### Possible causes

* Another request updated the same resource before this request completed, so the requested change now conflicts with the resource's current state.
* Multiple simultaneous requests from different threads, services, or plugins tried to modify the same resource.
* The request includes data or a state transition that conflicts with values already stored on the target resource.

### Possible solutions

* Retry the request after a short delay.
* Add retry logic with exponential backoff so overlapping updates can finish before you send the next request.
* Check the current state of the resource before retrying. Confirm that the update is still needed and that the desired change is not already present.
* Serialize updates to the same resource and wait for the first request to complete before sending another modification.
* Review the console message body or error details for more context about which part of the resource state caused the conflict.
* If the resource you are updating supports optimistic concurrency control, use `ETag` and `If-Match` to reject stale writes cleanly.

#### Additional resources

* [API mutation and conflict resolution](/docs/usage/mutation-and-conflict-resolution)
* [API best practices](/docs/usage/rest-api-best-practices)
* [Error Handling and Debugging](/docs/flex/developer/ui/errors-and-debugging)