Use the View activity in progress page to view the automation details of the selected queue, A Control Room administrator or user with the required permissions can Pause, Resume, or Stop an automation that is in progress.

The In-progress page displays a maximum of 1000 automations that are currently running along with a maximum of 1000 queued items. All the available filtering options in In-progress page is only applicable to these 2000 items.

The sorting of queued items is based on the Started on column. Therefore, only the oldest 1000 items are displayed if you have more than 1000.

Prerequisites

You must have the following permissions to view automation of a queue:
  • Queue Consumer or Queue Participant rights
  • Manage everyone's In progress activity feature permission
  • View and manage all scheduled activity from my folders activity permission (if you have access to the folder which has the WLM bot)
  • View and manage all scheduled activity permission (if you do not have access to the folder which has the WLM bot) as you are not the WLM automation owner and editing other user's WLM automation.
  • View my scheduled bots and Schedule my bots to run permissions to edit the WLM automation.
  • Edit my scheduled activity and Delete my scheduled activity permission as you are the WLM automation owner and editing the WLM automation.
  • View my bots to access WLM bot and Run my bots to edit a WLM automation using the Run bot with queue option.
  • View users and roles basic information permission when there is a Run-as user or any user list.
  • Run and schedule permission on the bots folder permission to give access to users on the bot for which the WLM automation is edited.
  • Consumer access to the queue user role (who is editing the WLM automation) needs to be part of the queue consumer.
  • Consumer access to the device pool user role (who is editing the WLM automation) needs to be part of the device pool consumer.
  • Access to the run-as users (run-as users who have been used in the WLM automation).
    Note: This is an optional recommendation. However, the users (who are editing WLM automation) should preferably have access to the run-as users (used in the WLM automation) through their role.
  • The WLM automation owner must be a Queue consumer with the following requirements:
    • Has access to the WLM automation (run and schedule permission).
    • Has access to run-as users (used in the WLM automation).
    • Is a Device pool consumer.
Note:
  • Though the View automation page is accessible from the Workload module, the page is launched from the Activity module.
  • You cannot Pause/Resume or Stop actions directly from the Activity > In progress page. For these actions, the Manage > Queues > View automation action is used.
  • Bots that are in the Queued status do not appear automatically on the In progress activity page. You must click the Refresh table button on the top-right corner of the activity table to view the queued bots.

Procedure

  1. Log in to the Control Room as administrator.
  2. Go to Manage → Queues.
  3. Hover over a queue with the In use status.
  4. Click the Actions menu (vertical ellipsis) and select View automation.
    This launches the Activity > Run bot with queue > View page.
  5. Choose one of the following options to manage the queue:
    OptionsDescription
    Automation details of the queue
    • The Bot name, path, dependencies, and if it requires administrative privileges to run in the Task Bot tab.
    • The Queue used to run the automation in the Queue tab.
    • Bot Runner details such as username, device, and user status in the Run as tab.
    • Details of the device pool in use to run the automation in the Device pool tab.
    • Details such as number of work items that were active, failed, pending, or completed processing in the Run history tab.
    Transfer ownership
    • Automation creator or a user associated with Manage ALL queues role can transfer the ownership of the WLM automation to another user. However, the new owner must have the following permissions:
      • Schedule my bots to run permission on the bot and its dependencies.
      • Consumer access on the queue
      • Consumer access on the device pool (on which the WLM automation is created)
      • Access to the Run-as users
      • All the privileges required for Run a bot with queue.

        For more information, see Using the Run with queue.

    • When transferring ownership, if you want to view the list of users (to whom the ownership can be transferred), you must have the View users and roles basic information permission.
    • After the ownership has been transferred, if the user does not have the View all schedules permission, an error is displayed on the Automation page.
    Pause The system pauses the distribution of work items from this queue to available bot runners in the device pool.
    Note: Until you resume this automation, any work items with Ready to Run status from this queue are not sent for processing.
    Resume The system starts distributing the work items from this queue.
    Note: Bots will fail to deploy if the WLM automation is paused and resumed when Bot Runners are mapped one-on-one with their default (single user) devices with Run on bot running devices option selected and one or more devices in the selected device pool is disconnected while the WLM automation is in paused state.
    Stop
    • The system stops distributing the work items from the queue associated with this automation.
    • Select No, cancel to return to the details page or Yes, stop to stop the work item processing and return to the Queues page.
    Edit Update the automation details such as processing time, queue, and device pool.

Next steps

Edit queues