Troubleshooting Steps

This page highlights the most common issues that may affect the functionality of the Robility Automation extension installed on Chrome and Edge browser and provides step-by-step solutions to help users diagnose and resolve them efficiently.

Exception with Open Web Browser Activity: Browser Not Responding

The “Open Web Browser” activity may throw an exception “Browser Not Responding. Close and reopen the browser” if the CPU utilization is high. In some cases, the activity may fail, but the browser might still launch. When CPU usage is high, system resources are heavily utilized, causing the browser take longer to launch, leading to a timeout or failure in the activity. Click here to know about the minimum system requirements for Robility. 

How to resolve this?

1. Optimize CPU Utilization: Ensure that CPU usage is stable. If necessary, verify that the system meets the hardware requirements for running Robility Designer and Runner.
2. Modify Activity Properties: In the “Open Web Browser” activity, set the “WaitForReady” property to “Complete” and increase the wait time to allow the browser to launch properly. 

If the issue persists, contact your Robility Support for further troubleshooting.

Extensions are removed automatically 

If the Robility Automation extension is removed automatically after installation, it may need to be reinstalled manually. This issue can occur due to various factors as below, 

1. User Profile Reset: If your browser profile is reset or corrupted, it may result in the removal of installed extensions.
2. IT Security Policies: Many organizations enforce group policies that restrict or remove extensions.

Click here to know how to install the extension. 

How to Resolve This Issue?

1. Manually reinstall the extension if it has been removed.
2. Verify browser settings to ensure extensions are allowed.
3. Whitelist Robility Automation in security software or IT policies.
4. Check with your IT administrator if the extension is being removed due to organizational policies.

If the issue persists, contact your Robility Support for further troubleshooting.

Extensions May Be Corrupted

If the Robility Automation extension displays the message “Extension may be corrupted,” it means the browser has detected potential issues that may affect its functionality. This could be due to security risks, firewall restrictions, or a corrupted installation.

Possible Causes:

1. Browser Security Alerts: Chrome and other browsers automatically check for extension integrity. If they detect unusual behavior or incomplete files, they may flag the extension as corrupted.
2. Firewall or Antivirus Interference: Certain security policies or firewall settings may block extensions, causing them to malfunction.
3. Incomplete Installation or Browser Updates: A failed installation or an interrupted browser update can corrupt the extension files.
4. Third-Party Software Conflicts: Some browser extensions or installed applications may interfere with Robility Automation, leading to corruption warnings.

How to Check and Fix the Issue?

1. Open Chrome Extensions by navigating to “Chrome:extensions”
2. Locate the Robility Automation extension and if marked as corrupted, you will see an option to “Repair” the extension.
3. Click the “Repair” button to allow Chrome to reinstall and fix the extension automatically.
4. Restart the browser and check if the issue is resolved.
5. Ensure your firewall, antivirus, or endpoint security is not blocking or restricting the extension.
6. If repairing does not resolve the issue, try removing and reinstalling the Robility Automation extension.

If the issue continues, contact your IT administrator for further troubleshooting.

Activity is not working properly, please close and re-open the browser and try again

If you encounter the message “Activity is not working properly, please close and re-open the browser and try again” while executing the robot, follow these steps to resolve the issue.

Step 1: Check If Extensions Are Installed and Enabled

The first step is to ensure that the Robility Automation extension is installed and enabled in your browser. If the extensions are not enabled, follow the instructions here to learn how to install them.

Step 2: Verify Native Messaging Host Functionality

If the extensions are installed and enabled but the issue persists, we need to check whether the Native Messaging Hosts are running. 

What is Native Messaging Host?

The Native Messaging Host is a communication port that enables interaction between the browser extension and the Robility activities. In Robility, the Native Messaging Hosts are:

a. RobilityChromeNativeApp (for Chrome)
b. RobilityEdgeNativeApp (for Edge)

Step 3: How to Check If the Robility NativeApp is Running

To verify that the Native Messaging Host is functioning properly, follow these steps:

1. Open Task Manager and navigate to the “Details” tab.
2. Check if RobilityChromeNativeApp.exe (for Chrome) or RobilityEdgeNativeApp.exe (for Edge) is running.
3. If the Native App is running or unavailable, move to the “Extensions” tab in your browser.
4. Enable “Developer Mode” at the top of the page.
5. Find the “RobilityAutomation” extension and click on the “Service Worker” link.
6. A new DevTools window will open, displaying the Native Messaging app logs.
7. If the log shows “Failed to connect”, it means the communication port is disabled, preventing the activities from working.

Note: The Native Messaging Host may be blocked by group policies in your organization. Click here to learn more about group policies.

Step 4: Checking the Native Messaging Host in the Registry Editor

We also need to check the Registry Editor because it contains essential configuration data for both the extension and its communication with Robility activities. If the registry entries are missing or misconfigured, it could prevent the extension from properly connecting with Robility activities.

Here are the two key registry entries you need to locate:

1. Extension ID – lgnoojafhdgcpllpgolgpmjjdejnneom (Robility Automation). This entry ensures that the extension is correctly installed in the browser.
2. Robility.Runtime.Automation – Facilitates communication between the extension and Robility activities.

Where to Find These Entries:

1. Verify Extension Installation: Navigate to: HKEY_USERS → Unique SID (e.g., S-1-5-21-2144601217-6038991-817656539) → SOFTWARE → Google → Browser → Extensions → lgnoojafhdgcpllpgolgpmjjdejnneom. This confirms that the extension is installed correctly in the browser.
2. Verify Extension-Activity Communication: Navigate to: HKEY_CURRENT_USER → SOFTWARE → Browser → Chrome → NativeMessagingHosts → Robility.Runtime.Automation.This ensures proper communication between the extension and Robility activities

Step 5: What to Do If Registry Entries Are Missing?

If the registry entries for RobilityAutomation or Robility.Runtime.Automation are missing:

1. Reinstall the Robility Extension: Reinstalling the extension ensures that these registry entries are created automatically. If the entries are not present after reinstalling, it indicates an issue with the installation process, and you may need to troubleshoot further with Robility Support team.

2. Check Group Policies: In some cases, group policies in your organization may prevent the registry entries from being created. Contact your IT administrator to ensure that these policies allow the installation and configuration of the required registry keys.