Skip to main content

Using the API I can stop, pause and resume a bot that is already running using the request below:

POST: {{ControlRoomURL}}/activity/manage

{
  "stop_executions": {
    "execution_ids": [
      "e5c8a404-0804-4448-ba89-56433db062c0",
      "3a19281a-5484-43c2-922e-e06be87f99d1",
      "e5c8a404-0804-4448-ba89-56433db062c0"
    ]
  },
  "pause_executions": {
    "execution_ids": [
      "e5c8a404-0804-4448-ba89-56433db062c0",
      "3a19281a-5484-43c2-922e-e06be87f99d1",
      "e5c8a404-0804-4448-ba89-56433db062c0"
    ]
  },
  "resume_executions": {
    "execution_ids": [
      "e5c8a404-0804-4448-ba89-56433db062c0",
      "3a19281a-5484-43c2-922e-e06be87f99d1",
      "e5c8a404-0804-4448-ba89-56433db062c0"
    ]
  }
}

 

How can I send a bot that is in queue status to history? Similar to what can be done directly in the control room

 

hiii

You can move the bot to history using the API by sending a specific request. Once the bot is stopped or paused, you can then archive or move it to history.

For anyone experiencing the same problem, there is an undocumented endpoint that does this job.

An example of what the request should look like, the body should only contain the request ID wrapped in double quotes

 

curl --location --request PUT 'https://name.my.automationanywhere.digital/v1/activity/auditunknown' \
--header 'X-Authorization: xxxxx' \
--header 'Content-Type: text/plain' \
--data '"e5c8a404-0804-4448-ba89-56433db062c0"'

 

Reply


Terms & ConditionsCookie settings