conflicting-command⚓︎

Problem

This is a description of a specific error response that you can receive when using the INVERS OneAPI via REST.¹

Check out our API Basics to learn more about the basic structure of all error responses and to find out how you should handle them.

{
    "type": "/problems/vehicle/conflicting-command",
    "type_documentation": "https://developers.invers.com/problems/vehicle/conflicting-command",
    "title": "The command cannot be executed because of a conflicting command's processing.",
    "status": 409,
    "detail": "…",
    "flow_id": "5e77e3e3-48ab-4955-8ab3-1c62339096ab"
}

Meaning⚓︎

This problem type occurs when the sent command conflicts with a command that is currently being processed by the vehicle. This is because not all vehicles support processing parallel commands.

Details⚓︎

Use the error response’s type property to handle specific errors and exception handling within your application. It’s comparable to an error code.
The detail property contains additional, more human-readable information about the problem or error. This is explanatory text and you should not have any exception handling and error handling code depend on it, as it may change.

Detail examples⚓︎

The following examples are typical texts which you might receive in the error response’s detail property. Note that it is not a complete list of all possible cases. Therefore expect to receive error responses with a detail property value not listed below.

Example problem details⚓︎

Vehicle ‘JQ7RP’ is already processing a conflicting command.

You are trying to send a command to the vehicle while it is already processing a conflicting (often identical) command.

Possible solutions:

Wait for the previously sent command to be completed and then send the command again.