What to do when Runner seems stuck when executing a new task?

In sporadic situations, the Runner may seem stuck after pulling a new task for execution.

In this situation, the execution is not started, and the Runner status remains as Executing task ... until the Runner is restarted.

Overall, the resources used by the previous execution, which have not been correctly finalized, can cause this type of problem. Thus, when the code attempts to reaccess these resources, a conflict occurs because the operating system considers these resources already "in use."

A classic example is the use of web drivers in web automation. Without proper finishing, the web driver may continue to run even after the process is completed, affecting the following executions.

A possible solution to this type of problem is to include treatments in the code to ensure that all resources allocated and used by the robot are finished correctly at the end of execution, even in cases where exceptions occur.

Following this good practice, every time the Runner performs this process, the environment will be "clean"; therefore, there will be no problems using specific resources.

Tip:

You can also always consult the log.txt file generated by the Runner to verify any exceptions during the environment preparation and process execution.

• Related Articles

• Keeping your remote session active when using Runner

  In some cases where a VM is used to run the automation, keeping the remote session active is necessary to avoid problems with the graphical interface, such as the OSError: screen grab failed error. This error is usually thrown when trying to perform ...

• Problems with blocking environments

  If you are trying to use BotCity's tools in a corporate environment, you may encounter some issues related to environment locks. Here are some of the most common issues when using the BotCity Studio SDK in blocking environments: Installation through ...

• What are the features and limitations of a Community license on BotCity Orchestrator?

  A new account that is created on BotCity Orchestrator has full access to the platform's functionalities (trial) for a period of 30 days. After this 30-day period, access to the platform continues in the same way; the only differences are some ...

• How to open a support ticket?

  If the knowledge base articles or our documentation portal did not resolve your questions or issues, you can open a new support ticket through the portal. After detailing the type of support you need, the ticket will be directed to our team so that ...

• Problems with dependencies when running an automation

  This problem usually occurs when the dependencies installation step is not done correctly. When running the code, a message is displayed regarding the installation of the packages: ModuleNotFoundError: No module named 'botcity’ The first step is to ...