Troubleshooting Bots
Below is a list of some common errors and how to fix them.
The bot has been configured to run in administrator mode, but the Laserfiche bot local tool is running as a standard user.
Elevate the Laserfiche bot local tool to run as an administrator.
- Navigate to the bot designer in Process Automation.
- Click Settings.
- Under Privileges, ensure Run bot as administrator is selected.
- Clear Run bot as administrator. Then, run the bot again.
- If there is no error, leave the option cleared.
- If there is an "Access denied" related error, continue to the next step.
- Close the Laserfiche Bots local tool on the workstation.
- Restart the local tool from the Windows Start menu by right-clicking the application and selecting Run as Administrator.
Bot instance terminated with the reason: the work item was canceled because there is no agent queue that has the required capability
- Navigate to the Manage tab in Laserfiche Bots.
- Select the bot that produced the error.
- Select the Run Settings tab in the right pane, and check the required capabilities for the bot.
- Navigate to Integrations in Process Automation, and then to Remote Agents.
- Open the Dedicated Bot Remote Agent.
- Select the Queues tab in the right pane, and check the capabilities in all queues.
- Ensure the required capabilities of the bot is subset of the capabilities of at least one queue of the Dedicated Bot Remote Agent.
Bot instances stuck in a queue but not running
- Navigate to Integrations, and then Remote Agents in Process Automation.
- Select Dedicated Bot Remote Agent.
- In the Queues tab to the right, check that there are workers assigned to the queue. If not, open the Dedicated Bot Remote Agent, and install workers based on instructions on the Workers tab. Then, on the Queues tab, select those workers under Worker assigned to queue. Click Save.
- On the machine where the worker is installed, ensure the LFPAAgent service for the worker is running.
- Ensure the Laserfiche Bots local tool (i.e., the Action History) is running on the same machine. Learn more.
- If all the bot instances are still in the queue, go to the machine where the worker is installed. Uninstall the worker, and then reinstall it.
- Ensure the worker is assigned to the queue, following the instructions in step 3.