Hi Richard,
The logging architecture has been changed in latest release(as per my knowledge there were many fixes on Logs in 17.1.6522). So it’s not just a fix for the issue in particular, but improvements for logs in general.
Yes, if it happens(hopefully not anymore) a batch file can be run to delete that folder.
I don’t have an exact answer to this but i can tell you how this folder gets populated. The Robot uses this folder(C:\Windows\SysWOW64\config\systemprofile\AppData\Local\UiPath\Logs\execution_log_data) to store temporary log files when the connection with Orchestrator is lost. Once the connection is restored it pushes the log messages to Orchestrator. This is a proprietary folder of Windows which sometimes gets corrupted therefore the logs are not sent to Orchestrator.
ashokkarale
Anil_G
Yoichi
yangyq10
postwick
chandreshsinh.jadeja
aravindbalineni123
Parvathy
aya
PRASHANT_GABHANE