Service Conflict

service-conflict · 409

Another service in this project already has this name, so nothing was written.

conflictField names the field and conflictValue the value it refused. It is almost always name; two websites created at once with the same name can meet on slug instead.

Besides the members every error carries, this type adds resourceType, conflictField and conflictValue.

Common causes

  • Another service in this project already uses that name.
  • The same create was sent twice and the first one went through, so the second meets its result.

How to fix the call

  • Read conflictField and conflictValue: together they say which value was refused.
  • Pick another name, or fetch the service that has it and use that one.
  • If the duplicate is your own retry, treat the call as done, not failed.
  • Send an Idempotency-Key header on writes, so a retry replays the first answer instead of colliding with it.

Example response

json
{
  "type": "service-conflict",
  "title": "Service Conflict",
  "detail": "A service with name 'storefront' already exists",
  "resourceType": "Service",
  "conflictField": "name",
  "conflictValue": "storefront",
  "requestId": "req-1785231000000-4f7b2c9ae",
  "timestamp": "2026-07-28T09:30:00.000Z",
  "path": "/v1/projects/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/services",
  "method": "POST",
  "instance": "POST /v1/projects/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/services",
  "status": 409,
  "docs": "https://ghaym.me/docs/errors/service-conflict"
}