conflict
Not allowed in the current state
BetaAPI v2 is in public beta: endpoints, fields and behaviour can change before general availability. See the changelog
Last updated
API v2
stoqapp.comAbout STOQContactPrivacy policyHelp center
Not allowed in the current state
Section titled “Not allowed in the current state”Code: conflict · HTTP status: usually 409
The request is well formed, but the resource’s current state does not allow it.
How to fix
Section titled “How to fix”Read the resource, pick an action valid for its state (or send force: true where the action allows it). Retrying unchanged fails again.
Example response
Section titled “Example response”{ "code": "conflict", "type": "https://docs.stoqapp.com/v2/docs/api-v2/errors/conflict/", "title": "Not allowed in the current state", "status": 409, "detail": "Cannot release: order is already cancelled. The resource's current state does not allow this. Read it, then choose an action valid for that state; retrying unchanged fails the same way.", "errors": [ "Cannot release: order is already cancelled." ], "details": [ { "code": "conflict", "message": "Cannot release: order is already cancelled.", "path": null, "value": null, "expected": null } ]}Every API v2 and MCP failure carries code and a type link to its page here. See Errors & Responses for the full envelope.
Was this page helpful?
Thanks for letting us know.
Still stuck? Ask Quinn or chat with support