Have your administrator move the task to history.

​@balu567 

You can try to reset your device with API Device (Remember that you must use the authentication API first.):POST - https://{yourcontrolroom}/v2/devices/reset Body:{ "deviceIds": {  "ids": d<Device ID>]  }}For all devices:Body:{  "allDevices": {  }}For occasions that are not specified:Body:{ "deviceIds": {  "ids": d-1]  }}

or 

Query below  : SELECT * FROM DEVICE_RUNAS_USER_USAGE where user_id != '-1';

Delete the record with the user id that got stuck 

I don’t have that Move activity to history option 

Try removing your device and adding it again.

If you’re unable to stop the current bot, a few things you can try:

If you have admin access, ask them to move the task to history – that usually clears the stuck bot.

You can also reset the device using the API:

POST - https://{yourcontrolroom}/v2/devices/reset  

Body: { "deviceIds": { "ids": s<Device ID>] } }  

Make sure to call the authentication API first.

 Some also check this query:

SELECT * FROM DEVICE_RUNAS_USER_USAGE WHERE user_id != '-1';  

If you find the stuck user ID, deleting that record might help.

If nothing works, try removing and re-adding your device — that fixed mine once. 

Hope it helps!