Datapool Inaccessible After Repository Migration: How to Fix ?

Datapool Inaccessible After Repository Migration: How to Fix ?

Issue

During the migration of robots to new repositories, a failure was identified: some old repositories that still contained logs and datapools had been deleted or lost access.

As a result, important information (execution logs and data pools) became temporarily inaccessible.

Cause

The issue occurred due to changes in the repository structure. During the migration process, the team removed or lost access to the old repositories before all content (logs and datapools) had been properly transferred.

It is important to note that, in our system, records are not permanently deleted — they are simply deactivated in the database.

Solution

To resolve the issue:

  • Administrator Hugo reactivated the old repositories in the database.

  • With the repositories reactivated, access to logs and datapools was restored.

  • The team then properly migrated the information to the new repositories.

Conclusion

If access to logs or datapools is lost during repository migration processes, please open a support ticket so the technical team can assist with reactivating the repositories for complete data migration.

    • Related Articles

    • Are Datapool Items Automatically Counted in Insights ?

      Question When using BotCity Maestro, are the items from the datapool automatically reflected in the Insights dashboard? Answer No. Datapool items are not automatically counted in the Insights tool. To have this information properly displayed in ...

    • Error Running Edge Browser via Orchestrator: How to Fix It?

      Issue During the execution of robots using the Microsoft Edge browser through the orchestrator, a specific issue was identified: the browser did not start correctly, whereas when running locally, the flow executed normally. The error presented was: ...

    • How to fix Python environment preparation failed error

      A very common error when executing automations through the Runner is Python Environment Preparation Failed. As the name suggests, the Runner fails when trying to prepare the Python environment for the robot's execution. This error occurs in different ...

    • Error Running Wizard.exe: How to Fix It?

      Issue When attempting to start the installation, configuration, or authentication process of the BotCity Runner using the wizard in .exe format, you may encounter difficulties opening the file. This error usually occurs due to company security ...

    • Why is the Runner stuck on "Executing task..." and how to fix it?

      Overview Occasionally, the BotCity Runner may appear stuck after retrieving a new task from the queue. In these cases, the status remains as: Executing task... and the automation does not actually start until the Runner is manually restarted. Likely ...