Edit a scheduled activity

Make changes to a schedule so that the automation is not skipped.

Prerequisites

Ensure that you are logged in to the Control Room as the administrator.

Edit the scheduled activity in order to:

Change the schedule type, date, or time.
Add or remove Bot Runners from the schedule.
Change the retry settings.

Note: The system redeploys the bots and dependencies only if there are updates to the bots or its dependent files.

Procedure

Hover over the Actions icon for the scheduled bot in the Activity table.
Click the Edit icon. ()

Make changes to the schedule details, bots, and devices, as required.

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 repeatedly	To schedule a bot to run at specific time on a given day, enter the: 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 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.

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 repeatedly

To schedule a bot to run at specific time on a given day, enter the:

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 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.

In the Missed schedule setting section, select Redeploy the schedule again to redeploy a schedule that was missed because of Control Room shut down.

Note: To ensure a successful deployment when using the Redeploy the schedule again option, you must start the compiler service before you restart the Control Room services.

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.
Select Device pools.
Select the pool from the list of available device pools.
Optional: Click the up or down arrow to set the selected device pools in preferred order.
Optional: Change the Automation priority from the General tab.
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.

Note: For schedules without a device pool, when one or more active run-as user devices are unavailable or disconnected, the bot deployment fails for all the run-as users in the schedule.

Automation 360