Resource Conflict

conflict · 409

The request is valid but clashes with the resource's current state, so the API refused it rather than apply it.

A clash over a duplicate value answers a type of its own, such as project-conflict.

This type adds no members to the ones every error carries.

Common causes

  • Another call applied or discarded the changeset, and this request tried to use it afterwards.
  • A rule about the resource itself refuses the operation: the production environment can't be deleted.

How to fix the call

  • Read detail; it names the rule that refused the request.
  • Read the resource again before deciding what to do. Its state moved, so a plan built on the old state is stale.
  • Don't retry blindly. If another caller applied the changeset, a retry applies nothing and hides the race.

Example response

json
{
  "type": "conflict",
  "title": "Resource Conflict",
  "status": 409,
  "detail": "The changeset is no longer open",
  "requestId": "req-1785231000000-4f7b2c9ae",
  "timestamp": "2026-07-28T09:30:00.000Z",
  "path": "/v1/projects/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/environments/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad402/changeset/apply",
  "method": "POST",
  "instance": "POST /v1/projects/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/environments/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad402/changeset/apply",
  "docs": "https://ghaym.me/docs/errors/conflict"
}