Skip to main content

state-conflict

HTTP status: 409 Conflict Type URI: https://docs.evinor.ai/problems/state-conflict

The request is well-formed, but it conflicts with the current state of the resource, so there is nothing for it to do. Evinor refuses it rather than silently treating it as done, so your integration learns that its picture of the resource is out of date. detail names the conflict.

Common causes​

  • Enabling a beat that is already enabled, or disabling one that is already disabled.
  • Resuming a beat that is not paused by its spend cap, or that is disabled.
  • Replacing a beat (PUT /v1/beats/{id}) with exactly the configuration it already has.

How to resolve​

Read the resource again (for a beat, GET /v1/beats/{id}) and decide from its current state. Retrying the same request unchanged returns the same conflict. See Beats.