Deactivate a sequence: automatic dispatch skips it, and it can no longer be started on a tour. It keeps its rank, so activating it puts it back in its place in the dispatch order. Nothing else is checked, so a sequence the rules of POST /sequences refuse now (a carrier or brick deleted since) can always be switched off. Deactivating an inactive sequence changes nothing and keeps its version; otherwise version advances. The response is the stored sequence, with its summary.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
401unauthorized
403The role of the API key does not allow this action. The key needs a role with the matching permission, for example full access.
404sequence not found: no sequence with this ID in the tenant of the key
409conflict - other requests kept changing the sequence (internalCode CONCURRENT_UPDATE). Nothing is written; send the request again.
