conflict

HTTP status

409

Title

Conflict

Code

conflict

What it means

The request conflicts with the resource's current state, for example acting on a run that is still active, or starting a fourth export while three are still pending or running in the same mode.

It is also the catch-all of status 409: an error of that status that has no more specific code answers with this one.

What to do

Read the resource again, then decide whether the action still makes sense.

Example

Errors are RFC 9457 problem details, sent as application/problem+json. See Errors for every field.

{
  "type": "https://docs.furniops.com/errors/conflict",
  "title": "Conflict",
  "status": 409,
  "code": "conflict",
  "detail": "An explanation of this occurrence.",
  "request_id": "req_…",
  "doc_url": "https://docs.furniops.com/errors/conflict"
}

Operations that answer it

• POST /v1/agreements/{kind}/acceptances
• DELETE /v1/assistant/conversations/{conversation}
• POST /v1/assistant/conversations/{conversation}/turns
• POST /v1/audit-events/{id}/undo
• POST /v1/billing/card
• POST /v1/billing/credits/purchases
• POST /v1/billing/credits/purchases/preview
• PATCH /v1/billing/details
• POST /v1/billing/preview
• POST /v1/billing/subscription
• POST /v1/billing/subscription/cancel
• POST /v1/billing/subscription/resume
• POST /v1/billing/subscription/scheduled-change/cancel
• PATCH /v1/brand
• POST /v1/brand/claims
• POST /v1/brand/claims/{id}/check
• POST /v1/brand/claims/{id}/withdraw
• POST /v1/catalogue/publish
• POST /v1/catalogue/visibility
• POST /v1/catalogue/withdraw
• POST /v1/exports
• POST /v1/mappings/{id}/confirm
• POST /v1/match-pairs/{id}/dismiss
• POST /v1/match-pairs/{id}/merge
• POST /v1/match-pairs/{id}/reopen
• POST /v1/merges/{id}/undo
• POST /v1/proposals/{id}/accept
• POST /v1/proposals/{id}/reject
• POST /v1/source-probes
• POST /v1/sources
• PATCH /v1/sources/{id}
• POST /v1/sources/{id}/categories
• POST /v1/sources/{id}/records
• POST /v1/sources/{id}/replay
• POST /v1/sources/{id}/runs
• POST /v1/sources/{id}/uploads
• POST /v1/uploads/{id}/complete
• POST /v1/webhook-endpoints/{id}/deliveries/{delivery}/resend
• POST /v1/webhook-endpoints/{id}/recover
• POST /v1/webhook-endpoints/{id}/test