Unable to connect and delete device to CR in community edition AA360. How do I resolve it ?
Unable to connect device to CR, it gives the following error-"System allows only a single device to be registered. If you need to replace your existing device you should delete it first."
Tried to delete the device from CR, it gives the following error - "Cannot delete device, as it is part of an active bot deployment"
Also there are bots pending in Activity-->In Progress which did not move to historical activity tab.
The screenshots of the errors is given in the order as stated above.
Resolution tried but not worked:
Restarted the bot runner machine several times.
Uninstalled bot agent and reinstalled it again.
Tried to authenticate using CR API but POST does not when provided with CR URL *(If there is workaround with API please let me know as I do not have much idea how to implement it)*
Read various articles but was of no use, did not solve the issue.
After successfully authenticating through the API Auth endpoint, I went through the procedure to reset a device based on its ID, but I get error 400 Bad Request "Reset type not set."
I have tried if it is due to syntax or data type in the following ways but it does not work
Is there a parameter missing from the POST request?
Option 1: With brackets and quotes
{ "deviceIds": { "ids": :"406"] }}
Option 2: With brackets and without quotes
{ "deviceIds": { "ids": :406] }}
Option 3: Without brackets and without quotes
{ "deviceIds": { "ids": 406 } }
v2/devices/list
v2/devices/reset
Note: I have carried out the process in Automation 360 Community Edition, which is where it does not allow deleting the device due to the error "Cannot delete device, as it is part of an active bot deployment", but the progress table is empty, I also ran the procedure in Automation 360 On-Premise getting the same result: "Reset type not set." Thanks for the help, I was looking in the documentation, but I can't find anything else related to the use of v2/devices/reset
Thank you very much for the help, I stay tuned
Best regards,
Hi @BOT.DEV & @Sausthava.G ,
Please check the API Query which you are trying to execute. Below is the correct syntax