Considerations for checking out multiple bots

There are certain considerations you have to keep in mind when checking out multiple bots.

  • You can check out up to 10 parent bots at a time.
  • You can only check out the latest version of the bot. You cannot select a specific version of the bot to check out.
  • During check out of multiple bots, the parent bots and their dependencies are either checked out, cloned, skipped, or overwritten depending on different scenarios.
The following table explains the different scenarios of the parent bots and their dependency behavior during check out of multiple bots.
Scenario Behavior
Parent bot not checked out by the current user The parent bot is checked out as part of the bulk checkout and is shown in the check-out section of the basic flow.
Dependency not checked out by the current user The dependency is checked out as part of the bulk check out and is shown in the check-out dependencies section of the advanced flow.
Parent bot is already checked out by the current user The parent bot is not re-checked out and is shown in the skipped section of the basic flow.
Dependency already checked out by the current user The dependency is not re-checked out and is shown in the skipped section of the advanced flow.
Dependency checked out by other users The dependency is cloned during bulk check out.
Parent bot already cloned by the current user and requiring a check out The parent bot is checked out as part of the bulk checkout, and the clone will be replaced with the checked out bot.
Dependency already cloned by the current user and requiring a check out The dependency is checked out as part of the bulk checkout, and the clone will be replaced with the checked out bot.
Dependency already cloned by the current user and is shown again for cloning in bulk check out The dependency is not re-cloned and is shown in the skipped section of the advanced flow.
Parent bot is in new status in private workspace During bulk check-out, the user is provided an option to overwrite the bot in the basic flow.
Dependency is in new status in the private workspace If the dependency is to be checked out, it is shown in the overwrite section of the advanced flow. If the dependency is to be cloned, it is shown in the cloned section of the advanced flow.