Conflict - 409
This type of error response is typically caused by requesting an action that cannot be completed due to some other action being required to allow the request.
Example of a Conflict error response:
{
"title": "Deployment could not be deleted.",
"status": 409,
"detail": "The requested deployment could not be deleted as it still contains an active device.",
}
Title | Detail |
---|---|
API Integration already exists in your org. | An API integration with the given name already exists within your organisation. Please provide a unique name. |
Deployment with name already exists within your organisation. | A deployment with the given name already exists within your organisation. Please provide a unique name. |
Cannot add device to deployment. | The device provided is already active on another deployment within your organisation. |
K-Cell in use on another deployment. | We cannot create the deployment with the requested K-Cell as it is active on another deployment within your org. Please contact Krucial to order an additional K-Cell or remove it from the other deployment. |
Device already exists within your organisation. | A device with the given DevEui already exists within your organisation. Please provide a different DevEui. |
Device Profile name already exists. | The name provided already belongs to another device profile. Please provide a different name. |
Plugin name already exists. | The name provided already belongs to another plugin. Please provide a different name. |
Webhook name already exists | The name provided already belongs to another webhook. Please provide a different name. |
Could not delete user as there needs to be at least one active user on the plugin. | There has to be at least on active user on an MQTT plugin. To delete this user, delete the plugin. |
User already exists. | A user with the desired username already exists on the Plugin resource. |