What Is HTTP 409 Conflict?

HTTP 409 Conflict explained, and what it means when you see it in CI/CD and deployments.

HTTP 409 means the request could not be completed due to a conflict with the resource state.

What it means

A 409 signals a state clash: creating something that already exists, an edit against a stale version, or two concurrent writes. The fix depends on the conflict.

When you see it in CI/CD

In CI, a 409 often means publishing a package version that already exists, or a concurrent deploy. For "already exists" cases, bump the version; for concurrency, serialize the job.

Key takeaways

• 409 means a state conflict.
• Often a duplicate version or concurrent write.
• Fix depends on the conflict cause.