Hi @1111202

The automatic opening of the Execution.log file in the %appdata%\Local\UiPath\log directory after an RPA operation is completed might occur if the “Open Log Folder” option is enabled in UiPath Studio settings. This setting is used for debugging purposes and allows quick access to the log files for reviewing any potential issues or errors.

If this behavior is happening only on terminal B and not on terminal A, it’s possible that there could be a difference in the Studio settings between the two terminals. Make sure to compare the settings in both terminals and ensure that the “Open Log Folder” option is disabled if you don’t want the log folder to open automatically after RPA operations are completed.

To change that settings follow the below steps:

  1. Open UiPath Studio on the terminal where you want to make the change (terminal B in your case).
  2. In UiPath Studio, go to the “Home” tab in the top menu.
  3. Click on the “Settings” button, usually represented by a gear icon. This will open the Settings window.
  4. In the Settings window, navigate to the “Execution” section or a similar section related to logging and debugging.
  5. Look for an option related to “Open Log Folder” or “Automatically Open Log Folder” and toggle the switch to disable this option. This will prevent the log folder from automatically opening after RPA operations are completed.
  6. Once you’ve made the change, remember to save the settings.
  7. Close and restart UiPath Studio to apply the updated settings.

Hope it helps!!

In the “Settings” tab there was no option to open the log automatically.

The version of Studio we are using is 2020.10.4.

Hi @1111202

In UiPath Studio version 2020.10.4, the option to control the automatic opening of the log folder after RPA operations may not be available through the Studio settings. In this case, the behavior might be due to a custom script or process specific to Terminal B or some other external factor.

To troubleshoot this behavior, you can consider the following steps:

  1. Check Workflow: Review the workflow and any custom scripts used in Terminal B. Ensure that there are no specific commands or activities that open the log folder explicitly.
  2. External Triggers: Determine if there are any external triggers or scripts running on Terminal B that might be causing the log folder to open.
  3. Environment Differences: Look for any differences in the environment between Terminal A and Terminal B. This includes UiPath version, Windows settings, or any third-party applications that might interact with UiPath.
  4. UiPath Traces: Check the UiPath Traces (Studio Log) for Terminal B to see if there are any custom log messages or activities that might be triggering this behavior.
  5. Consult UiPath Documentation: Consult the official UiPath documentation for version 2020.10.4 to see if there were any specific changes or known issues related to log folder behavior in this version.

Hope it helps!!

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.