What Information to Collect for MuleSoft RPA Issues

SYMPTOM

1. RPA Bot
2. RPA Builder
3. RPA Recorder

SOLUTION

1. RPA Bot

• Version of RPA Bot -

1. You can find the version number of the RPA Bot after logging in to RPA Manager and navigation to the Bot menu
2. Steps: Navigate to RPA Manager -> Bot Management -> Bots -> Check the particular Bot -> Bot Version

• Downloading the Bot's log file from RPA Manager -

1. Navigate to RPA Manager -> Bot Management -> Bots -> Check the particular Bot -> Click download (button on top right)
2. Attach the downloaded log file to the case

• Adjusting the Bot's log level

1. Navigate to Program files -> Mulesoft -> RpaBot -> MulesoftRPABot.exe.config - Open it in a text editor
2. Locate the <root> element within the XML structure and adjust the Log level, e.g. to "DEBUG".
3. Restart the Windows Bot Service so the changes are applied.

  

Note:

• To adjust the log level you need to have access to the system where the bot is running, as this cannot be changed using the RPA Manager
• Using "DEBUG" mode generates large amounts of log data and should only be used during replication of an issue and reverting it back to INFO immediately.
• Make sure the XML structure remains valid and only the value entry has been changed to avoid problems.

• Connection Test from RPA Bot Configurator

1. Navigate to Program files -> Mulesoft -> RpaBot -> Open the Bot Configurator executable -> RpaBotConfigurator
2. Send Screenshot by doing Test connection from Common and Secure Session

2. RPA Builder

• Version of RPA Builder

1. Navigate to Mulesoft RPA Builder -> From Menubar -> Help -> About Mulesoft RPA Builder

 

• Downloading RPA Builder Log file

1. Navigate to Mulesoft RPA Builder -> From Menubar -> Tools -> Open Mulesoft RPA Builder Log
2. The log file opens in a separate text editor window -> Download the log file and attach to the case

• Adjusting the RPA Builder log level

  You need to capture a more detailed log while replicating a scenario, in those cases, you need to increase the log level/severity

1. Navigate to Program files -> Mulesoft -> RPABuilder -> bin Config -> Open logconf.xml with a text editor.
2. Locate the <root> element within the XML structure and adjust the Log level, e.g. to "DEBUG".
3. Save the configuration file -> Restart the RPA Builder

Note:

• Using "DEBUG" mode generates large amounts of log data and should only be used during replication of an issue and reverting it back to INFO immediately.
• Make sure the XML structure remains valid and only the value entry has been changed to avoid problems.

• Connection test of RPA Builder

1. Navigate to Mulesoft RPA Builder -> From Menubar -> Options -> Repository
2. Send Screenshot by doing Test connection from Repository

3. RPA Recorder

• Version of RPA Recorder

1. Navigate to RPA Recorder ->  Click  "i" symbol (button on bottom left) - About dialog box contains the version.

 

• Downloading RPA Recorder Log file

1. Navigate to RPA Recorder -> Open settings via gear icon -> Open directory
2. The Windows Explorer opens with the Recorder's installation folder -> Open Logs folder -> Open log file based on timestamp

  

• Adjusting the RPA Recorder log level

1. Navigate to  Program Files -> Mulesoft -> RPARecorder -> MuleSoftRpaRecorder.exe.config -> Open it in a text editor
2. Locate the <root> element within the XML structure and adjust the Log level.
3. Save the configuration file -> Restart the RPA Recorder

Note:

• Using "DEBUG" mode generates large amounts of log data and should only be used during replication of an issue and reverting it back to INFO immediately.
• Make sure the XML structure remains valid and only the value entry has been changed to avoid problems.

• Collecting logs for Failed Recordings

1. Navigate to RPA Recorder -> Open settings via gear icon  -> Check the option “Generate debug file with a list of raw recorded events”
2. Repeat the recording session and reproduce the error
3. Locate the recorded session on the local drive via Open Directory. The recorder creates a folder for the current day to store session