Instance size Conflict
instance-size-conflict · 409
Another instance size in the catalogue already has this key, so nothing was written.
All pages
conflictField names the field and conflictValue the value it refused. Only operators reach the route that sends it.
Besides the members every error carries, this type adds resourceType, conflictField and conflictValue.
- Another instance size in the catalogue already uses that
key. - The same create was sent twice and the first one went through, so the second meets its result.
- Read
conflictFieldandconflictValue: together they say which value was refused. - Pick another
key, or fetch the instance size that has it and use that one. - If the duplicate is your own retry, treat the call as done, not failed.
- Send an
Idempotency-Keyheader on writes, so a retry replays the first answer instead of colliding with it.
json
{
"type": "instance-size-conflict",
"title": "Instance size Conflict",
"detail": "A instance size with key 'medium' already exists",
"resourceType": "Instance size",
"conflictField": "key",
"conflictValue": "medium",
"requestId": "req-1785231000000-4f7b2c9ae",
"timestamp": "2026-07-28T09:30:00.000Z",
"path": "/v1/admin/sizes",
"method": "POST",
"instance": "POST /v1/admin/sizes",
"status": 409,
"docs": "https://ghaym.me/docs/errors/instance-size-conflict"
}