Activate a sequence: automatic dispatch considers it again at its rank, and it can be started on a tour. The sequence is checked as a whole with the rules of POST /sequences, so one whose carrier or brick was deleted since, or whose name is empty, stays inactive and gets 400 until a PATCH fixes it. Activating an active 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… | |||
unauthorized
The role of the API key does not allow this action. The key needs a role with the matching permission, for example full access.
sequence not found: no sequence with this ID in the tenant of the key
conflict - other requests kept changing the sequence (internalCode CONCURRENT_UPDATE). Nothing is written; send the request again.