conflicting-setup-status⚓︎

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

Meaning⚓︎

This problem type occurs when a request concerning a vehicle can’t be executed because the vehicle’s setup is still in progress or has failed.

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

The Vehicle ‘JQ7RP’ is not ready for use because its setup status is not ‘SUCCEEDED’.

You are trying to send a command to a vehicle whose setup is still in progress or has failed.

Possible solutions:

Wait for the setup to finish or retry the setup process if it has failed.

The Vehicle ‘JQ7RP’ is not ready for use because a setup is currently in progress.

You are trying to do something with a vehicle that cannot be done while it is in setup.