EnvVar Conflict

envvar-conflict · 409

The changeset sets a new variable that another write created at the same moment, so nothing in it was applied.

conflictField names the field and conflictValue the value it refused.

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

Common causes

  • A service's launch wrote the same key while the changeset was being applied. Applying a key that exists replaces it, so this only happens to a new key.

How to fix the call

  • Read conflictField and conflictValue: together they say which value was refused.
  • Apply the changeset again: the key exists now, so the staged value replaces it.

Example response

json
{
  "type": "envvar-conflict",
  "title": "EnvVar Conflict",
  "detail": "A envvar with key 'DATABASE_URL' already exists",
  "resourceType": "EnvVar",
  "conflictField": "key",
  "conflictValue": "DATABASE_URL",
  "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",
  "status": 409,
  "docs": "https://ghaym.me/docs/errors/envvar-conflict"
}