Restore bots from Git repository
If your database is deleted or corrupted, you can restore all your bots and the associated dependent files from the Git repository to your new database. This restore option is available only for On-Premises deployments and not supported on Cloud deployments.
Prerequisites
Ensure the following before you restore your bots from Git:
- You must have a backup of the bots on Git.
- You must have the AAE_Admin role assigned.
- The Git restore process requires some downtime. When the restore process is
running, the following public workspace operations are disabled:
- Check-out
- Clone
- Run and schedule bots
- Run bots with queue
- Import and export bots
- When the restore process is running, the check-in operation is not allowed from the private workspace. However, you can use the private workspace for the rest of the operations.
- You can restore your bots to your empty or non-empty repository.
- You cannot abort an ongoing restore process.
Procedure
If the Git restore process fails after restoring some bots, you are redirected to the public workspace with the following options. Choose the required option to complete the restore process:
Option | Action |
---|---|
Revert restoration bots | This option clears all the bots that were
restored. Note: This option will delete the
public bots that were restored from the Git
repository. |
Restart restoration | The Git restore process restarts from where it ended. |
Keep only the restored files | This option retains whatever files were restored and will exit the restore process. |