In this version V 6.2.2.2 of Robility Runner, delay in writing log to local machine and Robility manager has been addressed. No other changes have been made as part of this release.

Bug Fixed:

User reported that there is delay in logs being written to local machine.  Writing log to local path and transfer to the server was carried out RobilityLogger.exe and now the functionality has been split between Runner.exe for writing log to local machine and transfer of log data to the server is carried out by Robilitylogger.exe.   A task has been created to trigger the logger exe, which runs every one minute to check if the exe is active and if found inactive logger.exe will be re-launched. To avoid duplication of log details in the manager, which might occur due to the failure of logger.exe. A file with count of log that has been sent to the server is maintained in the local machine. Thus the delay in log generation has been avoided.

Limitations:

• The number of characters that can be printed using the write log activity while getting executed through Runner is limited to 300 characters.
• The logs displayed in the manager might be delayed by 3 to 4 minutes due to the latency in elastic server receiving log data through the logger exe.