Enabling verbose-level Runtime logging
Capturing verbose-level Runtime logging files can help to diagnose and resolve errors, when requested by the Pega Robotic Automation support team. For example, if you are designing an automation with Robot Studio, and it is not working as expected, verbose logging can help you or Pega Support determine what the issue is.
To set the system to capture verbose information in the logging files, first determine the location of the RuntimeConfig.xml file. The default location of the RuntimeConfig.xml file can differ, depending on the version of the product.
For Robot Runtime version v19.1: %appdata%\Pegasystems
For Robot Runtime version 8.0 SP1 and earlier: %appdata%\Openspan
Modifying the RuntimeConfig.xml file
To enable verbose logging, perform the following steps:
Before starting Robot Runtime, open the RuntimeConfig.xml file in a text editor.
Find type=“OpenSpan.Diagnostics.Publishers.FilePublisher" near the top of the document. On the same line, set the publisher mode to on.
Towards the bottom of the file, find the <LogCategories>section. For each category, change the logLevel attribute from its current value to 4.
Save and close the file.
Re-create the issue that you experienced. Take note of when you began the steps to re-create the issue and when you finished.
After you re-create the issue, turn off the logging by setting the publisher mode to off for type=“OpenSpan.Diagnostics.Publishers.FilePublisher”.
Collect the log file, timestamps, and any additional notes about the issue and provide them to your Support Engineer for analysis.
You can find the log files in the same folder as the RuntimeConfig.xml file. The file is assigned the name RuntimeLog.txt.
Previous topic Introduction to the Robot Inspector Next topic RPA automated testing