Conflict

The request clashes with the current state: it already exists, or it is not possible yet. 409.

Pattern

conflict.*

Raised with

fail()

Intents

Statuses

409

View as Markdown

Intents

conflict.duplicate409

It would create something that exists: a taken handle or email, a second follow

conflict.state409

Not possible right now: create your page first, already published

Raising one

Name what went wrong. The intent sets the status, the message the caller sees, and any log it writes.

// It would create something that exists: a taken handle or email, a second follow
return fail('conflict.duplicate', 'That handle is already taken.');

// Not possible right now: create your page first, already published
return fail('conflict.state', 'Create your page first.');

The caller gets (conflict.duplicate)

Terminal

HTTP 409

{
  "ok": false,
  "error": "That handle is already taken.",
  "code": "conflict.duplicate"
}

Is it a conflict error?

Find the row that describes your case, and use the domain on the right.

If the problem is
Use
The caller’s request was wrong: unreadable, incomplete, or a value that breaks a rule. 400 or 422.
request.*
No valid credentials: nobody signed in, an expired session, a bad token or secret. 401.
auth.*
Valid credentials, but not allowed to do this. 403.
permission.*
The thing asked for is not there, as far as the caller may know. 404.
record.*
The request clashes with the current state: it already exists, or it is not possible yet. 409.
conflict.* this page
Too many requests, or an allowance used up. 429.
limit.*
Our fault or a dependency’s. The caller sees a generic message; the details are logged. 5xx.
failure.*

For registry authors

Starter intents. These are the intents prongs add errors puts in your registry, raised with fail(). Change the messages to suit your app, and the statuses through the status.* intents they are built from.