Delete bots from the public workspace if you are a Control Room administrator or have the Delete from Public permission, or from your private workspace if you are a Bot Creator.
Before you begin
To delete a bot, ensure the following:
- In the public workspace, you must have the Control Room administrator role or the Delete from Public permission at the folder level.
- You must have the Delete from Public permission on the folders and files that the bot depends on.
- In a private workspace, you must have a Bot Creator license.
About this task
Before you delete a bot, note the following:
- You cannot restore a deleted bot from either the
public or private workspace. Confirm that you no longer need a bot
before you delete it. Note: After you delete a bot, wait atleast 5 seconds before you create a bot with the same name in the same folder. Otherwise, an error can be displayed.
- You cannot delete a bot or any of its clones if they are referenced by other bots. Before deleting a bot, identify and remove all the references to it and its clones.
Procedure
Managing bot dependencies and cloned bots
- Identify dependent bots: Review all the bots that reference the bot to be deleted through Run Task Bot actions, workflows, or other automation dependencies. Remove these references before attempting deletion.
- Review cloned bots: If the platform created cloned versions of the bot, verify whether the clones are referenced by other bots.
- Resolve clone dependencies: A cloned bot cannot be deleted until all references to that clone are removed.
- Recommended deletion sequence:
- Remove dependencies from clones
- Delete cloned bots
- Delete the original bot
- Deletion behavior: If clones are deleted before the original bot, all associated bot files are removed from the repository. If the original bot is deleted before its clones, some files can remain in the repository.