Schedule a bot

Schedule a bot to run at a specific time.

Prerequisites
Ensure you are logged in to the Control Room as the administrator or a user with the following
permissions:
 Schedule my bots to run
 Schedule permission at folder level for specific bots and their dependencies
 Access to run-as users (Bot Runners) that you can add to the schedule
Note:Automation will fail in the following cases:
 If any of the bot dependencies are missing.
 If you do not have folder privileges on the dependencies.
 If you do not have the scheduling permissions.

Procedure
1. Navigate to Manage > Scheduled.
2. Click Run bot.
3. Click Schedule bot.
4. Add the scheduling details for the bot.
Note:The value of the Start date is always later than or equal to the current date. If the start
date is the current date, the scheduled time cannot be less than the current time.
Option Definition
Run once To run the bot at a specified time, enter the:
Start date
Default value is the current day.
Start time
Default value is roundup to the next half-hour.
Time zone
User's system time zone
Run To schedule a bot to run at specific time on a given day, enter the:
repeatedly
Start date
Default value is the current day.
End date
The default value field is blank.
Start time
Default value is roundup to the next half-hour.
Time zone
User's system time zone
Note:
When the daylight saving is enabled and if the Start date is set for a schedule, the Start
date is shown in the time zone to which it belongs to and not as per the user's current time
 Option Definition
zone. However, Next occurrence is shown in the time zone (user's system time zone) as per
daylight saving time.
For example, for a schedule created on 15th March in GMT time zone, the Start date is
shown as Mar-15th which belongs to GMT time zone. Later, when daylight saving is ON and
if you edit or view this schedule in the month of August in BST time zone, next occurrence is
shown as current August month date which belongs to BST time zone.

5. In the Missed schedule setting section, select Redeploy the schedule again to redeploy a
schedule that was missed because of Control Room shut down.
When the Redeploy the schedule again option is selected, schedules missed because
of Control Room shut down are automatically redeployed after the Control Room is restarted.
An audit log entry is also added showing the Event type as Schedule misfired.

6. Select the bot to schedule.

 Latest version: Click Latest version tab to select the latest version of the bot.
 Labeled version: Click Production version tab to select the labeled version of the bot.
Available bots are displayed along with any Input values and dependencies. If the production
label option is selected for the parent bot, the corresponding dependent bots with the
production label are also automatically selected. If any of the dependent bots do not have the
production label applied, the latest version of the bot is selected.
7. Select the Bot Runner user from the Available bot runners list.
Note:If a run-as user (Bot Runner) does not appear in the list, ensure the user scheduling
the bots is assigned a role that provides access to the appropriate run-as users.

8. Click the right arrow (→) to add your selection.

9. Optional: Select Device Pools.
 Select the pool from the list of available device pools. If any of the selected run-as users does
not have the bot running device, a device pool is required. You can select up to 25 device
pools per schedule.
10. Optional: Click the up or down arrow to set the selected device pools in preferred order.
When a bot is deployed, the Control Room selects the first available device based on the order
in which you organized the device pools. If none of the devices are available at the time of
deployment, the bot is queued.
11. Enter the Name.
12. Optional: Enter a description.
13. Select the Automation priority from the General tab.
Set the priority to high, medium, or low based on your requirements for resource optimization.
The default permission is set to medium.
14. Click Schedule bot.
The Schedule bot option remains disabled until all the required items, such as bots, schedule
details, and devices are selected.
The number of times a bot is deployed depends on the run-as users (Bot Runners) selected for
the schedule. Consider the following scenarios:
 The number of run-as users selected is two, and both the users have the bot running device:
The bot is deployed twice on the two run-as users and their bot running devices.
 The number of run-as users selected is three, and only one of the users has the bot running
device. In this case, you must select the device pool. If the device pool has only two devices,
the bot is deployed three times on both the devices in the device pool and also on
the bot running device of the third user.
 The number of run-as users selected is three, and none of the three users has the bot running
device: In this case, you must select the device pool. If the device pool has only two devices,
the bot is deployed twice on both the devices in the device pool, and the third request
for bot deployment is queued. The bot is deployed only when a device becomes available in
the device pool.
 The number of run-as users selected is two, and none of the two users have the bot running
device: In this case, you must select the device pool. If the device pool has four devices,
the bot is deployed twice on any available two devices in the device pool.
 Enterprise 11: Schedule a bot
To run a bot at a later point in time, on a periodic basis, or at a specific point in time, use
the Schedule bot page.

Prerequisites
The following permissions are required:
 View everyone's In progress activity
 View my scheduled bots
 View my bots
Note:
 You can access only the folders for which you have the Run and Schedule permission.
 You cannot schedule Attended Bots from the Control Room. Only Unattended Bots are
available for the schedule operation.

You can schedule a bot from any of the following Control Room pages:
 Activity > In progress
 Activity > Scheduled
 Bots > My bots
 Devices > Bot runners and bot creators

Procedure
1. Click the Schedule bot link in the appropriate page, such as the In progress, Scheduled, My
bots, or Bot runners and bot creators page.
The Schedule bot page is launched.
2. From the Select a TaskBot area, click one of the folders depending on your requirements.
The Type and name of the available bots are shown on the right side in a tabular format.
3. Click a bot to select a TaskBot depending on your requirements.
The Select option is enabled.
4. Click Select.
The bot is ready to be scheduled. You can view the dependencies of the selected bot in
the Review dependencies for <bot name> section.
Note:When you click Select, the option label changes to Replace. This provides you an option
to select another bot and replace the selected bot.

Although, you can schedule a bot, automation fails in the following cases:
 If any of the bot dependencies are missing
 If you do not have the folder privileges on the dependencies
 If you do not have the Run and Schedule permission (shows a red dependency icon - )
5. Click the Next link.
 The Schedule and Devices tab is shown. You can choose from two options to schedule
a bot: Run once or Run repeatedly.
 Run once: Use this option to run the bot once on a given day at x hour. When you select this
option, set the start date and start time.
 Run repeatedly: Use this option to schedule your bot to run every x minutes per hour on a
given day. When you select this option, select the start date, end date, and start time.
 Enter the Start date either manually in MM/DD/YYYY format or by using the pop-up calendar.
The default value of the Start date field is set to the current day of your local system.
Enter the End date if you are using the Run repeatedly option. The default value of the End
date field is blank.
Note:If the value selected in the Start date field is the current day, the scheduled time has to
be greater than the current time. Also, the value of the End date field has to be later than or
equal to the value in the Start date field.

 Enter the Start time using the drop-down list to quickly set the time value. The list
contains predefined time values in the 12-hour format at intervals of 15 minutes. You can also
manually set the time value in the 12-hour format. However, this is not available for the
selection in the drop-down list. The default value of the Start Time field is rounded off to the
closest half-hour that is 15 minutes away. For example, if the current time is 11:22 AM, it will
display 12:00 PM.
 Time Zone: While creating and editing a schedule, you can select the Time Zone with the start
time. The default value of the Time Zone is set to the current location your system.
Note:A schedule is run based on the Time Zone selected when creating or editing a schedule.

For more information about selection of time in schedules by considering Day Light Saving
Time (DST) switch over, see Daylight Saving and Time Zone Selection in Schedules.
6. After selecting the Run once or Run repeatedly options, click a device of your choice from
the Available devices area and use the arrow button to move it to the Selected devices area.
The list shows the devices connected and disconnected to the Control Room.
Note:You can select only bot runner devices that are connected. If a device is not connected,
it is not enabled. Also, if the device does not appear in the list, ensure that an active bot
runner session is running on the device.

7. Optional: Select the Run bot runner session on control room when you want the Control
Room to use the RDP of the Bot Runner sessions and run it in its local memory.
Use this option if you face issues with Auto Login. You can also choose to set the RDP screen
resolution of the Bot Runner with the Set bot runner screen resolution option and ensure
that the screen resolution of the Bot Creator and Bot Runner match and the bot executes
successfully.
For more details, see Guidelines for RDP-based bot deployment.
 Note:When this option is selected, a separate audit log for run bot deployment and Bot
Runner session is logged in the Control Room. See Audit logs for run bot deployment and bot
runner session.

After the device is added to the list of selected devices, the Upcoming schedules for that
device are shown. This helps you to decide whether to deploy another schedule or not.
8. Click the Next link.
The Name and Description tab appears.
9. Enter a name and description in the General area and click the Schedule bot option.
The bot is added to the Activity table of the Scheduled activity page.
Note:The Schedule bot option remains disabled until all the required items, such as bots,
schedule details, and devices are not selected.

1. As we can’t monitor 24 hours, so we will be checking the scheduled

bots, that whether we get any issues or not.
2. If we found any issues then we need to raise tickets and intimate
them about the issue and provide a fix and redeploy to production.
3. Else we need to check the mails whether the flow went fine or not if
we found any data mismatch then we should investigate and provide
fixes.
4. We can provide 1 or 2 lines of code can be fixed else we need to raise
a CR (Change request). Once after getting the approvals from the prod
team we can deploy in to prod.
5. Also we need to check whether it need a new bot or not, if needed
then we can create new bot and test and deploy them.
6. If needed any supporting for migration activities we are doing that
also, migration done from 10.xx, 11.xx to A360.
7. If needed any emergency deployment request, then we are sending
the intimation mail about the stop and trigger the same in the backup
machines.
8. According to the priority we will trigger the bots.