# CONFLICT

> 409: the request conflicts with the current state of what it changes.

Nothing was written for your request. Either another change reached the same title, episode or list at the same
moment (from your app and the member's phone, for example) and yours lost the race, or the change does not fit the
current state, which `detail` names.

| `detail` | What it means | What to do |
|---|---|---|
| none | Another change ran at the same moment. | Retry after a short pause. |
| `remove_rewatches_first` | You asked to remove a movie's first watch while it still has rewatches. | Remove the rewatches first (`DELETE /v1/history/movies/{id}`), or leave it. |
| `unlisted_rewatches` | The movie has rewatches imported without a date, which the API does not list. | The member removes them in the app. |
| `not_watched` | You logged a rewatch of an episode the member has not watched yet. | Mark the first watch with `PUT /v1/history/episodes/{id}/{season}/{number}`. |
| `remove_in_app` | You asked to remove a season or whole-show rewatch, which counts on every episode it covered. | The member removes it in the app. |
| `duplicate_list_name` | The member already has a list with this name. | Pick another name. |
| `ITEM_ALREADY_IN_LIST` | The list holds the same title under another id. | Nothing to add. |
| `stale_item_set` | The titles you sent are no longer the list's titles. | Read `GET /v1/lists/{id}/items` again, then reorder. |

## How to fix it

Without a `detail`, retry: `PUT` and `DELETE` are safe to retry, and a `POST` too as long as you send the same
`Idempotency-Key`. With one, follow the table: retrying the same request gets the same answer.
