ROBIN Agent is the module responsible for sending messages and commands between ROBIN Studio, ROBIN Orchestrator and ROBIN Robot:

  • when a robot is launched from any component of the platform, the launch is controlled via the ROBIN Agent;
  • real-time transfer of robot execution logs to ROBIN Orchestrator 2.0;
  • transmission of information about the status of the machine and its current workload to ROBIN Orchestrator.
Delivery optionFunctioning OptionPath to the installed application
For me onlyApplicationC:/Users/<userName>/AppData/Local/Programs/Robin Platform/2.0.0/Agent
For all usersOperating system serviceC:/Program Files/Robin Platform/2.0.0/Agent

Robot Player "Agent" settings tab

In the "Agent" section, it is possible to customize the logging of the ROBIN Agent.

For Standalone delivery

Characteristics of the settings of the "Agent" tab are presented in the table.

For Standalone delivery

No.SettingCharacteristic
1Log of frequent operationsIf "true" is specified, the agent's frequently executed operations will be recorded in its log
2Save all messagesIf "true" is specified, the "messages.data" file will contain all messages exchanged between the agent and other components of the Robin platform.

Click on the "Save" button and restart the ROBIN Agent to save the changes.

For Enterprise and Cloud delivery

No.

Settings

Characteristics


Checkbox

Log of frequent operations

If this parameter is enabled, the agent's frequently performed operations will be recorded in its log. For example, ping commands. After updating the parameter, you need to restart ROBIN Agent

Checkbox

Cache robot dependencies

If caching is disabled, the dependencies will be removed from the machine after the robot is finished. Therefore, each time the robot is restarted, the action packages will be restored

Checkbox

Cache robots

If caching is disabled, then after the robot completes its work, its file will be deleted from the machine. Therefore, each time the robot is restarted, it will be downloaded to the machine again

Checkbox

Reconnection interval

The interval for reconnecting the agent to the server when the connection is broken. The value is specified in seconds. The minimum value is "5

Checkbox

Save all messages

Saving all incoming and outgoing messages. After updating the parameter, you need to restart ROBIN Agent

Checkbox

Interval for sending machine data

The interval for sending data about the resources of the machine. The value is specified in seconds. The minimum value is "5". After updating the parameter, you need to restart ROBIN Agent

Checkbox

Log .NET dependencies restore

If this parameter is enabled, information about the download .NET dependencies will be recorded in the agent log

Checkbox

Log Python dependencies restore

If this parameter is enabled, information about the download Python dependencies will be recorded in the agent log

Checkbox

Log Java dependencies restore

If this parameter is enabled, information about the download Java dependencies will be recorded in the agent log

Special conditions

When running robots in Robin Studio Enterprise, when restoring files with long names to a folder that itself has a long name, you may encounter limitations related to the MAX_PATH path length, which is defined by the Windows API as 260 characters.

If caching of robot dependencies is disabled, when restoring files in Robin Studio Enterprise there is not enough path length to download one of the engine's dependencies, moreover, after the robot is finished, the dependencies will be deleted from the machine. Therefore, each time the robot is restarted, the action packages will be restored.

To do this, you need to check the ROBIN Agent settings:

  1. If "Do NOT cache robot dependencies" is selected in the ROBIN Agent settings,

then when running the robot on a .NET action (such as Show message), the robot terminates with an error that is related to the length of the MAX_PATH path.

Result 

Package recovery error

Starting with Windows 10 version 1607, MAX_PATH with dependency caching disabled restrictions have been removed for many common Win32 file and directory functions. However, the application in use must agree to the new behavior.

To enable the new long path behavior for each application when robot dependency caching is disabled, some conditions must be met.

You can see more details here: https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=registry#enable-long-paths-in-windows-10-version-1607-and-later

This problem can be solved by setting the registry manually. To do this, set the  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystemLongPathsEnabled registry to 1.

2. In versions higher than 2.24.0 the list of Robot Player "Agent" settings has been improved and in order for packages to be restored correctly and the robot to start and run without errors, it is sufficient to enable dependency caching in the ROBIN Agent settings.

Then, when running the same "Show message" action, the long path packets are fully restored and the robot works without error.

Displaying the status of the ROBIN Agent

Agent status is displayed by the connection status indicator in the workspace in the form of a circle with the letter "A".

Relevant for versions: Standalone, Enterprise, Cloud.

ROBIN Player:

If there are problems with the connection to the ROBIN Agent, there may be problems starting the robot. To diagNo.se possible problems, an Agent connection status indicator is placed on the application interfaces.

There are the following options for displaying the user information about the status of the Agent:

Standalone delivery option:

  • Green - ROBIN Player is connected to the Agent
  • Gray - ROBIN Player is No.t connected to the Agent

Enterprise\Cloud delivery option:

  • Green - ROBIN Player is connected to an Agent, Agent is connected to Orchestrator
  • Gray - ROBIN Player is No.t connected to the Agent
  • Red - ROBIN Player is connected to the Agent, the Agent is No.t connected to the Orchestrator
  • Yellow - ROBIN Player is connected to the Agent, reconnection to the Orchestrator is in progress

ROBIN Studio

Standalone delivery option:

  • Green - ROBIN Studio is connected to the Agent
  • Gray - ROBIN Studio is No.t connected to the Agent

Enterprise\Cloud delivery option:

  • Green - ROBIN Studio is connected to an Agent, Agent is connected to Orchestrator
  • Gray - ROBIN Studio is No.t connected to the Agent
  • Red - ROBIN Studio is connected to the Agent, the Agent is No.t connected to the Orchestrator
  • Yellow - ROBIN Studio is connected to the Agent, reconnection to the Orchestrator is in progress

If there is a problem connecting to the ROBIN Agent, the first thing you can do is try to solve the problem by restarting it. To do this:

  1. In the case when the installation "For me only" was performed
    • Stop Robin Robot Player - right-click on the program icon in the tray and select the "Quit" menu item.
    • Open the directory where ROBIN Agent is installed (see path above).
    • Find and run the Kill.Robin.Agent.exe program in the directory and wait for it to complete
    • Find and run the Robin.Agent.exe program in the directory and wait for it to complete
  2. In the case when the installation "For all users" was performed
    • Stop ROBIN RobotPlayer by right-clicking on the program icon in the directory and select the "Quit" menu item
    • Open the task manager (Ctrl-Alt-Del -> "Task Manager")
    • Go to the "Services"  section
    • Find the Robin.Agent.Service process in the Services section
    • Stop the process by right-clicking on the process name in Task Manager and selecting the "Stop" menu option
    • Wait for the Robin.Agent.Service process to stop completely
    • Start the Robin.Agent.Service process again, right click on the process name in the Task Manager, select the menu item "Run"
    • Wait for the Robin.Agent.Service process to start (the status "Running" appears in the Services bar)
    • Launch Robot Player by double-clicking the program icon on the Desktop of the workstation

Names and descriptions of configuration parameters

DeliveryParameter

Name

Description
StandaloneAllowLogFrequentOperationsLog of frequent operationsIf this parameter is enabled, the agent's frequently performed operations will be recorded in its log. For example, ping commands. After updating the parameter, you need to restart ROBIN Agent.
SaveAllMessagesSave all messagesIf the parameter is enabled, all messages exchanged by the agent with other components of the Robin platform will be recorded in the "messages.data" file. After updating the parameter, you need to restart ROBIN Agent.

Enterprise


AllowLogFrequentOperations

Log of frequent operationsIf this parameter is enabled, the agent's frequently performed operations will be recorded in its log. For example, ping commands. After updating the parameter, you need to restart ROBIN Agent.
CacheRobotDependenciesCache robot dependenciesIf caching is disabled, the dependencies will be removed from the machine after the robot is finished. Therefore, each time the robot is restarted, the action packages will be restored.
CacheRobots
Cache robotsIf caching is disabled, then after the robot completes its work, its file will be deleted from the machine. Therefore, each time the robot is restarted, it will be downloaded to the machine again.
ReconnectIntervalSecondsReconnection intervalThe interval for reconnecting the agent to the server when the connection is broken. The value is specified in seconds. The minimum value is "5".

SaveAllMessages

Save all messagesSaving all incoming and outgoing messages. After updating the parameter, you need to restart ROBIN Agent.
SystemUsageIntervalSecondsInterval for sending machine dataThe interval for sending data about the resources of the machine. The value is specified in seconds. The minimum value is "5". After updating the parameter, you need to restart ROBIN Agent.
LogDotnetRestoreLog .NET dependencies restoreIf this parameter is enabled, information about the download .NET dependencies will be recorded in the agent log.
LogJavaRestoreLog Java dependencies restoreIf this parameter is enabled, information about the download Java dependencies will be recorded in the agent log.
LogPythonRestoreLog Python dependencies restoreIf this parameter is enabled, information about the download Python dependencies will be recorded in the agent log.

Cloud









AllowLogFrequentOperations

Log of frequent operationsIf this parameter is enabled, the agent's frequently performed operations will be recorded in its log. For example, ping commands. After updating the parameter, you need to restart ROBIN Agent.

CacheRobotDependencies

Cache robot dependenciesIf caching is disabled, the dependencies will be removed from the machine after the robot is finished. Therefore, each time the robot is restarted, the action packages will be restored.

CacheRobots

Cache robotsIf caching is disabled, then after the robot completes its work, its file will be deleted from the machine. Therefore, each time the robot is restarted, it will be downloaded to the machine again.

ReconnectIntervalSeconds

Reconnection intervalThe interval for reconnecting the agent to the server when the connection is broken. The value is specified in seconds. The minimum value is "5".

SystemUsageIntervalSeconds

Interval for sending machine dataThe interval for sending data about the resources of the machine. The value is specified in seconds. The minimum value is "5". After updating the parameter, you need to restart ROBIN Agent.

SaveAllMessages

Save all messagesSaving all incoming and outgoing messages. After updating the parameter, you need to restart ROBIN Agent.

LogDotnetRestore

Log .NET dependencies restoreIf this parameter is enabled, information about the download .NET dependencies will be recorded in the agent log.

LogJavaRestore

Log Java dependencies restoreIf this parameter is enabled, information about the download Java dependencies will be recorded in the agent log.

LogPythonRestore

Log Python dependencies restoreIf this parameter is enabled, information about the download Python dependencies will be recorded in the agent log.
  • Нет меток