conflicting-state⚓︎

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-state",
    "type_documentation": "https://developers.invers.com/problems/vehicle/conflicting-state",
    "title": "The command cannot be executed due to the current state of the vehicle.",
    "status": 409,
    "detail": "…",
    "flow_id": "5e77e3e3-48ab-4955-8ab3-1c62339096ab"
}

Meaning⚓︎

This problem type occurs when the sent command cannot be executed due to the state of the vehicle.

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⚓︎

Unable to execute the command while the vehicle ‘JQ7RP’ is moving.

You are trying to lock the vehicle while the vehicle is moving.

Possible solutions:

Wait for the vehicle’s state to be suitable for the command to be executed. In this case, the vehicle can be locked when it is not moving.