Managing Runner

Health Check

The Health Check tab in the Runner application is an essential tool for monitoring and diagnosing the bot’s health status. It provides critical insights into the bot’s readiness and operational condition, particularly when errors or unexpected issues occur during execution.

When a bot encounters an error, the Health Check tab should be the first point of reference. This feature helps identify potential issues and ensures the bot meets all necessary conditions for successful execution. By regularly reviewing the health status, users can prevent downtime and maintain smooth operations.

The Health Check tab highlights several important aspects:

1. Error Diagnosis: When a bot fails or encounters an issue during execution, the tab provides details about its health status, offering clues about what might have gone wrong.
2. Execution Readiness: It also verifies that the bot fulfills all required conditions for execution through the Runner. These conditions include system configurations, resource availability, and connectivity, which are vital for the bot to operate without interruptions.
3. Troubleshooting Guidance: By reviewing the health status, users can quickly identify problems, such as missing dependencies or misconfigurations, and address them efficiently.

Refer to the image below for a detailed overview of the prerequisites and conditions that must be fulfilled for the bot to execute successfully. 

Overview

The main screen of the Health Status tab displays four critical conditions that must be satisfied for the bot to run. These conditions are visually represented, and the bot will only execute if all four are marked with a green check. If any condition is incorrect, the following actions may be required:

1. Error Indication: If there is an issue with a condition, the corresponding status will turn red. The bot will not proceed and moves to the “ToCheck” status, to halt the execution until the error is resolved.
2. Repairing Issues: Use the Repair button to address plugin-related issues. This action removes and reinstalls the plugin, resolving most errors and allowing the bot to function. If the bot still fails to launch, review the log file to identify and resolve the underlying problem.
3. Scheduler Issues: If the scheduler’s configuration or functionality is problematic, attempt to repair the bot first. If repairing does not resolve the issue, use the Reset button as an alternative solution.
4. Browser Extensions: Errors related to Chrome or Edge extensions can be fixed by enabling the Robility Automation extension in the respective browsers. Open the affected browser, navigate to the extensions section, and activate the required plugin to restore functionality.