conflict
The request is well formed, but the current state does not allow it.
| Status | Title | type |
|---|---|---|
409 | Conflict | https://substrat.net/errors/conflict |
What it means
The input is fine. The thing it addresses is in a state where this cannot happen now. reason names the rule that refused, and it is the member to branch on.
When it is returned
- A lifecycle transition the declared machine does not allow from the current state (
reason: invalid_transition). - A uniqueness rule: a name, slug or hostname already taken.
- A tenant or scope that is not active, on the control plane (
reason: scope_not_active). - An engine invariant, such as a record that is immutable once exported.
What it carries
reason: A slug the refusing module owns, narrowing the code. The platform's own are snake_case, but the wire does not enforce a grammar, so compare it as an opaque string. Branch on it; never show it.
Relayed from a scope store, it may also carry storeCode and storeBody. See the body for the members any problem may carry.
What to do
Re-read the current state, then decide. The same request conflicts again unless something else changes the state first. Branch on reason, not on detail: the sentence is written for people and may change.
In /openapi.json
Documented on every operation's failure responses.