Skip to main content

Troubleshooting AutomatR Orchestrator

Troubleshooting AutomatR Orchestrator can involve various aspects, from system issues to process problems. Here's a list of detailed troubleshooting procedures for AutomatR Orchestrator:

Checking Orchestrator Logs in AutomatR Orchestrator​

AutomatR Orchestrator generates various logs that are invaluable for diagnosing issues, monitoring performance, and troubleshooting errors. AutomatR Orchestrator logs provide insights into the health and operation of your robotic process automation (RPA) environment. To effectively manage your AutomatR Orchestrator instance, it's essential to review these logs for errors, warnings, or exceptions regularly. Typically, these logs can be found in the "C:\ProgramData\AutomatR\Logs" directory on the server where AutomatR Orchestrator is installed.

Here's a detailed brief section regarding the process of checking AutomatR Orchestrator logs in AutomatR Orchestrator:

Accessing AutomatR Orchestrator Logs:

  1. Log Directory Location: AutomatR Orchestrator logs are usually stored in the "C:\ProgramData\AutomatR\Logs" directory on the AutomatR Orchestrator server. Access this directory through the server's file system.

  2. Log Categories: The logs are categorized based on different components and areas of AutomatR Orchestrator. Common log categories include:

    • AutomatR.Orchestrator.dll: Logs related to Orchestrator's core functions and services.
    • AutomatR.Jobs.dll: Logs related to job scheduling, execution, and job processing.
    • AutomatR.Executor.exe: Logs associated with the Robot executor component.

  3. Log Files: Within each log category, you will find individual log files. These files contain timestamped entries of events, errors, and exceptions.

Reviewing AutomatR Orchestrator Logs:

  1. Error Identification: Start by scanning the logs for any entries that indicate errors or exceptions. Errors are often marked with red or highlighted text. These entries can provide crucial information about what went wrong.

  2. Timestamps: Pay attention to the timestamps of log entries. This helps determine when an issue occurred and can be useful for correlating events across different log files.

  3. Stack Traces: Error entries often include stack traces, which provide a detailed report of what happened leading up to the error. These stack traces can be valuable for pinpointing the root cause.

  4. Severity Levels: Logs typically categorize entries by severity levels, such as INFO, WARN, ERROR, or FATAL. Focus on entries with higher severity levels, as these are more likely to represent critical issues.

  5. Patterns and Trends: Look for recurring patterns or trends in the logs. Identifying common errors or issues can help in diagnosing broader problems.

Troubleshooting and Resolving Issues:

  1. Error Message Details: When you encounter an error or exception in the logs, pay close attention to the accompanying error message. This message often provides context about what failed and why.

  2. Error Code Lookup: If an error code is included in the log entry, consult AutomatR's official documentation or support resources for explanations and potential solutions.

  3. Log Rotation: Orchestrator logs may rotate periodically to avoid becoming too large. Ensure that you have access to archived log files if necessary.

  4. External Tools: Consider using log analysis tools or scripts to help automate log monitoring and analysis, especially for large-scale Orchestrator environments.

By regularly reviewing Orchestrator logs, you can promptly identify and address issues, ultimately ensuring the stability and reliability of your RPA processes. Additionally, proactive log monitoring can help prevent downtime and disruptions, as well as aid in the optimization of your AutomatR Orchestrator instance.

Clearing Cache and Cookies in AutomatR Orchestrator​

AutomatR Orchestrator provides a web-based interface that allows users to manage and monitor their robotic process automation (RPA) processes. Occasionally, users may encounter issues with the AutomatR Orchestrator web interface, such as slow performance, login problems, or display errors. In such cases, one effective troubleshooting step is to advise users to clear their browser's cache and cookies. This action can help resolve problems related to cached data and session cookies, ensuring a smoother experience with the AutomatR Orchestrator platform.

Here's a detailed brief section regarding the clearing of cache and cookies in AutomatR Orchestrator:

Why Clearing Cache and Cookies Matters:

  1. Stale Data: Over time, browsers store various types of data in the cache, including images, scripts, and stylesheets. This cached data can become outdated, causing discrepancies with the latest AutomatR Orchestrator content.

  2. Session Cookies: Session cookies are used to maintain user sessions and preferences. If a session cookie becomes corrupted or outdated, it can lead to login or session-related issues.

Steps to Advise Users:

1. Inform Users:

  • In the event of AutomatR Orchestrator web interface issues, inform users that clearing their browser's cache and cookies may resolve the problem.

2. Clearing Cache and Cookies:

  • Browser Menu: Instruct users to open their browser's menu. This is typically found in the upper-right corner represented by three vertical dots or lines.

  • Settings or Options: Within the menu, guide users to find the "Settings," "Options," or "Preferences" section.

  • Privacy and Security: In the settings, users should look for a "Privacy and Security" or "Privacy" option.

  • Clear Browsing Data: Encourage users to locate and select the "Clear Browsing Data" or similar option.

  • Choose Data to Clear: Users will typically be presented with checkboxes to choose which data to clear. In this case, instruct them to select "Cookies and other site data" and "Cached images and files."

  • Clear Data: Finally, users should initiate the process to clear the selected data. The specific button for this action may be labeled "Clear data," "Clear browsing data," or something similar.

3. Reloading AutomatR Orchestrator:

  • After clearing cache and cookies, advise users to close and reopen their browser.

  • Have them access AutomatR Orchestrator and log in again. They should experience improved performance and fewer interface issues.

Important Notes:

  • Users should be aware that clearing cookies will log them out of websites where they were previously authenticated. Therefore, they'll need to log back in to any websites they were using.

  • If issues persist after clearing cache and cookies, advise users to check their browser extensions, update their browser, or switch to a different browser to determine if the problem is browser-specific.

Clearing cache and cookies is a standard troubleshooting step for web-based applications and can often resolve issues related to cached data and session problems. It should be included as part of regular user support procedures for AutomatR Orchestrator to ensure a smooth and error-free user experience.

Validating Bot Connection in AutomatR Orchestrator​

Bots are the essential workforce in your robotic process automation (RPA) ecosystem, and their proper connection to AutomatR Orchestrator is crucial for seamless automation. To ensure that bots are correctly connected to AutomatR Orchestrator, it's essential to verify and validate the bot's settings in the Bot configuration. This involves checking and confirming that the Bots are properly configured to communicate with AutomatR Orchestrator, ensuring the successful execution of automation processes.

Here's a detailed brief section regarding the validation of bot connections in AutomatR Orchestrator:

1. Access AutomatR Orchestrator:

  • Begin by logging into your AutomatR Orchestrator instance as an administrator or a user with sufficient permissions to access and manage Bots.

2. Navigate to Bots:

  • In AutomatR Orchestrator, navigate to the "Bots" tab, typically found in the left-hand menu. This section provides an overview of all the Bots registered with AutomatR Orchestrator.

3. Verify Bot List:

  • Examine the list of Bots in AutomatR Orchestrator. Check for the presence of the Bots you expect to see. If any Bots are missing, they may not be correctly registered.

4. Review Bot Status:

  • Pay close attention to the status of each Bot. Ensure that the Bots are listed as "Available" and not "Disconnected" or "Unlicensed." Disconnected or unlicensed Bots will be unable to execute tasks.

5. Bot Configuration:

  • Click on a specific Bot to view its configuration. Here, you can review details such as the Bot's name, type, machine, username, and environment. Ensure that this information aligns with the actual Bot configuration.

6. Machine Association:

  • Confirm that the Bot is associated with the correct machine in AutomatR Orchestrator. The machine should correspond to the physical or virtual machine where the Bot is installed.

7. Username and Password:

  • Double-check the username and password configured for the Bot. This information should match the credentials required to log in to the machine where the Bot operates.

8. Machine Key:

  • Verify the machine key associated with the Bot. The machine key acts as a secure token that allows the Bot to authenticate and communicate with AutomatR Orchestrator.

9. Bot Type and License:

  • Ensure that the Bot type (attended, unattended, etc.) and license status are correctly set. If a Bot is unlicensed, it will be unable to perform tasks.

10. Connectivity Testing:

  • AutomatR Orchestrator provides a "Test Connection" option in the Bot configuration. Use this feature to test the connection between the Bot and AutomatR Orchestrator. A successful test confirms that the Bot can communicate with AutomatR Orchestrator.

11. License Status:

  • Check the Bot's license status. Ensure that the Bot is properly licensed to execute tasks. Unlicensed Bots won't be able to perform automation jobs.

12. Environment Assignment:

  • Verify that the Bot is assigned to the correct environment within AutomatR Orchestrator. Environments help organize and manage Bots based on their roles and responsibilities.

13. Monitoring and Maintenance:

  • Regularly monitor the Bots in AutomatR Orchestrator to ensure that they remain connected and licensed. Perform maintenance tasks, such as updating credentials or adjusting settings, as needed.

By following these steps to validate Bot connections in AutomatR Orchestrator, you can ensure that your RPA workforce is correctly configured and ready to execute automation tasks as required. Detecting and addressing any configuration discrepancies or issues promptly can help maintain the efficiency and reliability of your automation processes.

Checking Bot Status in AutomatR Orchestrator​

AutomatR Orchestrator relies on a fleet of Bots to execute automation tasks and processes. Monitoring and maintaining the status of individual Bots is critical to ensuring the smooth operation of your robotic process automation (RPA) environment. This involves verifying that Bots are available, licensed, and ready to execute tasks. Here are the steps to check and troubleshoot Bot status in AutomatR Orchestrator:

  1. Log in to your AutomatR Orchestrator web interface using the appropriate credentials.

  2. In the Orchestrator web interface, navigate to the "Bots" tab. This is where you can view the status and details of all Bots connected to Orchestrator.

  3. On the "Bots" tab, review the list of Bots. Check the "Connection" column to ensure that Bots are in the "Connected" state. Bots in this state are ready to receive and execute tasks.

  4. Confirm that each Bot has a valid license. In the "Bot Type" column, licensed Bots should display the license type (e.g., Attended, Unattended or Studio.). Unlicensed Bots may appear as "None" in this column.

  5. If you encounter unlicensed Bots, investigate the cause. Licensing issues may require reconfiguration or updates. Ensure that your organization's AutomatR licensing is up to date.

  6. Select an individual Bot in the list and click on it to view more details. Check the Bot's logs for any errors or issues that may be affecting its operation. The logs may provide insights into the cause of Bot unavailability.

  7. If any Bots are marked as "Disconnected" or "Offline," investigate the reasons for their offline status. Common causes include network issues, Bot service errors, or issues on the Bot machine itself.

  8. Troubleshoot offline Bots by examining network connectivity, ensuring the Bot service is running on the Bot machine, and addressing any hardware or software problems on the Bot machine.

  9. Examine the Bot's settings and configurations to verify that it is correctly associated with the appropriate machine, environment, and Orchestrator. Incorrect settings can lead to operational issues.

  10. If a Bot is unresponsive or not updating its status in Orchestrator, consider restarting the Bot service on the respective machine. This can resolve connectivity issues and restore the Bot's availability.

  11. Ensure that your organization has sufficient licenses for the number of Bots in use. Running more Bots than you are licensed for can lead to licensing issues and unavailable Bots.

  12. Consider implementing automated monitoring and alerting systems that notify administrators of Bot availability issues in real-time. This proactive approach allows for quick intervention and issue resolution.

By regularly monitoring Bot status, addressing licensing and availability issues, and promptly troubleshooting offline or unlicensed Bots, you can maintain the reliability and efficiency of your RPA processes in AutomatR Orchestrator. Effective Bot management is essential for the success of your automation initiatives.

Reviewing Queues and Processes in AutomatR Orchestrator​

AutomatR Orchestrator serves as the central hub for managing and monitoring your robotic process automation (RPA) processes. A crucial aspect of Orchestrator's oversight is the continuous review of queues and processes to ensure that automation tasks are executed efficiently and without interruptions. This involves inspecting the status of queues and processes, checking for items stuck in queues, identifying failed jobs, and addressing potential bottlenecks in the RPA workflow.

Here's a detailed brief section on "Reviewing Queues and Processes in AutomatR Orchestrator":

1. Queue Status:

  • Access the Queues: Log in to the AutomatR Orchestrator web interface and navigate to the "Queues" section. This is where you can view and manage queues that hold automation tasks.

  • Check Queue Status: Examine the status of queues to ensure that they are processing items as expected. Look for queues that are active and have a low number of pending items. This indicates efficient task handling.

  • Stuck Items: Investigate any queues that have items stuck in a "Pending" or "Retry" status. Stuck items may require intervention to understand and resolve the underlying issue.

  • Retention Policy: Review the queue's retention policy to ensure that it aligns with your process requirements. Retention policies dictate how long items remain in the queue before being automatically removed.

2. Process Status:

  • Access the Jobs Page: In Orchestrator, navigate to the "Jobs" or "Jobs" section. This is where you can monitor the execution status of RPA processes.

  • Check for Failed Jobs: Identify any RPA processes or jobs that have failed. Failed jobs may require investigation to determine the cause of failure, such as exceptions, errors, or data issues.

  • Investigate Errors: If a job has failed, access the logs and error messages associated with the job to understand the specific issue. This information can help in troubleshooting and rectifying errors.

  • Job Dependencies: Examine jobs with dependencies to ensure they are triggered as expected and that processes run in the correct sequence.

3. Bottleneck Identification:

  • Review Execution Times: Analyze the execution times of RPA jobs. Identify processes that consistently take longer to execute than anticipated, as these may indicate potential bottlenecks.

  • Resource Utilization: Monitor the usage of system resources, such as CPU and memory, during job execution. High resource consumption may lead to performance bottlenecks and should be addressed.

  • Concurrency and Parallel Processing: Consider optimizing your processes for concurrency and parallel execution, especially if your RPA infrastructure has multiple Robots.

4. Maintenance and Optimization:

  • Regular Cleanup: Periodically clean up queues by removing completed and outdated items to prevent unnecessary clutter.

  • Process Optimization: Continuously optimize RPA processes to improve efficiency and reduce execution times. This may involve streamlining workflows, minimizing manual intervention points, or enhancing error handling.

  • Performance Tuning: Optimize Orchestrator settings and configuration to align with your organization's needs and resources, such as adjusting the number of concurrent jobs or Robot assignments.

By regularly reviewing queues and processes in AutomatR Orchestrator, you can maintain a well-organized and efficient automation environment. Detecting and addressing issues promptly ensures that your RPA tasks are executed smoothly, helping you achieve your automation goals while minimizing disruptions and delays.