Artifactory "409 Conflict" cannot overwrite release in CI

The target repository has "Handle Releases" with overwrite disabled, so redeploying the same version returns 409 Conflict. Artifactory is protecting immutable releases; the version already exists.

What this error means

A second deploy of the same release coordinates fails with HTTP 409 and a message that the repository does not allow overwriting or that the artifact already exists.

Artifactory

Received status code 409 (Conflict) from server:
{ "errors" : [ { "status" : 409, "message" : "Not allowed to overwrite the released artifact 'libs-release-local:com/acme/app/1.0.0/app-1.0.0.jar'" } ] }

Common causes

Re-publishing an existing release version

The version was already deployed and the release repo rejects overwrites to keep published releases immutable.

CI re-runs the release job without bumping the version

A retried or duplicated pipeline deploys the same coordinates again, colliding with the existing artifact.

How to fix it

Bump the version for a new release

Increment the version so the coordinates are new.
Re-run the deploy against the release repo.
Use the snapshot repo for iterative, overwritable builds.

Terminal

mvn versions:set -DnewVersion=1.0.1
mvn deploy

Deploy snapshots to a snapshot repo

Route non-final builds to a -snapshot repository that permits overwrites, keeping the release repo immutable.

pom.xml

<snapshotRepository>
  <id>artifactory</id>
  <url>https://mycompany.jfrog.io/artifactory/libs-snapshot-local</url>
</snapshotRepository>

How to prevent it

Keep release repos immutable and never redeploy the same version.
Use snapshot repos for iterative builds.
Make CI fail early if the release version already exists.