Errors and recovery¶
Agents should treat errors as typed workflow outcomes, not as invitations to guess another project or endpoint.
| Error | Meaning | Correct response |
|---|---|---|
authentication required |
No usable credential reached the server | Reconnect or authenticate; do not write |
task not found |
The task is absent from the authenticated project | Stop; do not recreate it |
write_context_required |
A mutation omitted the binding context | Rediscover the schema and provide the selected profile |
resource_mismatch |
The selected resource is not this server | Stop and fix the connection profile |
instance_mismatch |
The request targets another instance | Stop and reconnect to the intended instance |
project_mismatch |
The request targets another project | Stop; do not switch projects silently |
version_conflict |
Another session changed the task first | Re-read and reassess the work |
idempotency_conflict |
A retry key was reused with different input | Use a new logical operation or correct the payload |
duplicate_work_receipt |
The session receipt already exists | Re-read the task; do not append a duplicate |
Never log authorization headers, tokens, database URLs, or full memory bodies while diagnosing a failed client.