---
title: "HTTP 409 Conflict — What It Means & How to Fix It"
description: "HTTP 409 Conflict: The request conflicts with the current state of the target resource. Common causes, fixes and how to monitor it."
url: https://uptrack.app/http/409
---

# HTTP 409 Conflict

The request conflicts with the current state of the target resource. The server cannot complete the request because it would create an inconsistency — such as a duplicate record or a version mismatch.

## What does HTTP 409 mean?

The request conflicts with the current state of the target resource. The server cannot complete the request because it would create an inconsistency — such as a duplicate record or a version mismatch.

## Common causes

1. 1  
Attempting to create a resource that already exists, e.g., registering a username or email that is already taken.
2. 2  
Optimistic concurrency conflict — two users edited the same record simultaneously and the second save conflicts with the first.
3. 3  
A state transition that is not allowed, e.g., trying to publish a document that is already published or cancelling an order that has already shipped.

## How to fix it

1. 1  
Read the response body for details about the conflict. Most APIs explain which field or constraint was violated.
2. 2  
For concurrency conflicts, fetch the latest version of the resource, merge changes, and retry the request.
3. 3  
For duplicate-key conflicts, check if the resource already exists before creating it, or use an upsert operation if your API supports it.

## Monitor for HTTP 409 errors

A sudden spike in 409 errors may indicate a race condition or broken deduplication logic in your application. Uptrack alerts you to status code changes so you can investigate before data integrity issues escalate.

## Catch HTTP errors before your users do

Start free, or choose a plan, for 30-second monitoring and alert confirmation.

[See plans](https://uptrack.app/pricing)

from $3/mo · 30-day money-back guarantee

## Other HTTP status codes

- [HTTP 408 Request Timeout](https://uptrack.app/http/408)
- [HTTP 410 Gone](https://uptrack.app/http/410)
- [HTTP 405 Method Not Allowed](https://uptrack.app/http/405)
- [HTTP 413 Payload Too Large](https://uptrack.app/http/413)
- [HTTP 404 Not Found](https://uptrack.app/http/404)
- [HTTP 403 Forbidden](https://uptrack.app/http/403)
- [HTTP 415 Unsupported Media Type](https://uptrack.app/http/415)
- [HTTP 401 Unauthorized](https://uptrack.app/http/401)
- [HTTP 400 Bad Request](https://uptrack.app/http/400)
- [HTTP 422 Unprocessable Entity](https://uptrack.app/http/422)
- [HTTP 429 Too Many Requests](https://uptrack.app/http/429)
- [HTTP 451 Unavailable For Legal Reasons](https://uptrack.app/http/451)
- [HTTP 500 Internal Server Error](https://uptrack.app/http/500)
- [HTTP 502 Bad Gateway](https://uptrack.app/http/502)
- [HTTP 503 Service Unavailable](https://uptrack.app/http/503)
- [HTTP 504 Gateway Timeout](https://uptrack.app/http/504)
- [HTTP 304 Not Modified](https://uptrack.app/http/304)
- [HTTP 302 Found](https://uptrack.app/http/302)
- [HTTP 301 Moved Permanently](https://uptrack.app/http/301)
- [HTTP 520 Web Server Returns Unknown Error](https://uptrack.app/http/520)
- [HTTP 522 Connection Timed Out](https://uptrack.app/http/522)
- [HTTP 204 No Content](https://uptrack.app/http/204)
- [HTTP 201 Created](https://uptrack.app/http/201)
- [HTTP 200 OK](https://uptrack.app/http/200)
