Edit a scheduled activity
- Updated: 2025/02/12
Make changes to a schedule so that the automation is not skipped.
Prerequisites
- Manage my activity
- Manage ALL scheduled activity from my Folders
- Manage ALL scheduled activity
Note: User role must be associated with the View
users and roles basic information permission in order to view or edit a
schedule.
Edit the scheduled activity in order to:
- Change the name.
- 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
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.