Hi.
I have been running jobs for years and have been able to see logs for each job. Since 9am this morning (2.5 hours ago) jobs are running, however there are no logs showing in Orchestrator when I click “Show logs for this job”. I had one job fail to write a local file due to hard drive space issues, however there was 1gb free, and now there is over 9gb.
Any ideas why I can’t see logs being created and viewed?
Thanks
Craig…
are you on cloud orchestrator?
can you check if any default fitlers are present?
Also you can right click in chrome go to inspect and see networks tab if you are seeing any failures there when you click on jobs tab
cheers
Hi @Anil_G.
I’m on Cloud Orchestrator and the default filters are Time: All, and Level: Trace (All).
For jobs that ran prior to 9am this morning I can view the logs and see entries. Jobs are that do not have any entries and when I opne the logs screen it says “No data to display yet”.
When I went into Inspect I can see the following error:
Tracking Prevention blocked access to storage . Do that mean our IT department or something else has made a change to permissions?
If you can edit site settings then try adding UiPath in exception list and check
cheers
Hi @Anil_G,
Thanks for the suggestion.
I checked and it seems the browser’s Tracking Prevention may be blocking UiPath Orchestrator storage/cookies for newer log sessions. Older logs are still visible, but new job logs are not loading and show “No data to display yet”.
I’ll try:
I’ll also check with our IT team in case any recent security policy or browser update changed permissions.
Thanks again.
You can also personally try these fixes quickly:
cloud.uipath.com*.uipath.comIf the jobs themselves are successful but logs alone are missing, it is usually:
According to IT there haven’t been any updates done today. I not fully across the process buy my understanding is that the Logs are written to the Local Machine, and then transferred to Orchestrator. Is this correct?
I will login to the server containing the robot and try and locate the local logs to confirm local access hasn’t been changed. Then try and figure out why they aren’t appearing.
Based on your error:
Tracking Prevention blocked access to storage
This is browser-related, not UiPath or IT server issue.
Try this first
@Monali_Vekariya and @Anil_G . I logged into Orchestrator using another PC and and also in an InPrivate window and on both occassions I can see logs for all jobs prior to 9am, and then after then all jobs don’t contain any logs. I can see the jobs and their status so Orchestrator can communicate with the Robot Machine (in this case its Unattended).
It appears like either the logs where never created (I logged in to the Robot Machine and navigated to the logs folder and there weren’t logs there after 9am. Although this may be correct.) or the logs were created and shipped to Orchestrator but not being displayed for some reason.
So I don’t think it’s browser based given the same this occurs on multiple PC’s and browsers.
Check if you have enough space on local disk C: on the impacted robot VM to create and store the logs.
Check if you have LiteDB error mentions in Event Viewer for Application, as this can tell more details.
Since you checked on different PCs and browsers and still no logs after 9 AM, this is clearly not a browser issue. Also, because logs are not even present on the robot machine, it means the robot is not generating or sending logs at all. This usually happens if something broke at the robot level in your case, the disk space issue earlier could have impacted logging.
The best thing to try is restarting the UiPath Robot service or the machine, and then run a job again. Also quickly check that log level in Orchestrator is not restricted (should be Info/Trace). If it still doesn’t work, then it could be an NLog/config issue or a temporary cloud ingestion problem.
Hi everyone.
I logged into the Robot machine and the logging in Assistant is set to Info. I have restarted the UiPath services on the machine. I also logged out and disconnected the robot. After all of these the logs are still not appearing. I have another Azure Virtual Desktop (UAT) and ran the same process on that robot machine and the logs appear.
IT wants to restore the server from mid-week to see if that works. Before they do that I was wondering if there is anything else I should look at? Definately machine based issue.
Thanks for everyones help.
Craig…
Since it’s working fine on UAT and not on this machine, the issue is definitely on the robot machine. Before restoring the server, just check a few things: open the NLog.config file and see if it got corrupted (this can happen after disk space issues), check Event Viewer for any UiPath or logging errors, and also verify if any logs are being created in the local UiPath logs folder. You can also run a simple workflow with just a Log Message to test. If nothing gets logged, then logging is likely broken at the machine level. If all these checks fail, then restoring the server makes sense.
Hi @Monali_Vekariya .
I checked the NLog.config file and it opened without issues and it appeared identical to the version on the UAT machine. I also went into the Log folder for the particular user and I can see the 2026-05-15_Execution.log file for today and its includes all the entries I would be expecting to see.
So the logs are being written but not being sent to Orchestrator.
I also logged onto the Robot as a different user and ran a process via Assistant. I can see a 2026-05-15_Execution.log file for this user containing the logs for the job I just ran, however these are not appearing in Orchestrator so its not specific to a given user.
So I decided to unstall UiPath from the Azure Virtual Desktop and do a reinstall. When I reinstalled I connected it to Orchestrator via UiPath Assistant and ran some jobs. The logs appeared as expected. However, when I did the install it didn’t install the Unattended Robot as a windows service so whenever I logged off the Unattended Session ended. I then re-installed again and ensured that the Unattended Robot was selected and also the Robot as a Service. This was then linked to Orchestrator and jobs can be run without being logged in. The issue is that now the logs have stopped again.
Does anyone have any thoughts as to why the logs are no longer appearing when running as a windows service? I have another UAT AVD setup the same and using Windows Service as that shows logs fine.
Thanks
Craig…
It was a corrupt LiteDB file. Deleted the contents of the following folder:
C:\Windows\System32\config\systemprofile\AppData\Local\UiPath\Logs\execution_log_data
Then restarted the UiPath Robot service which created a new database file and log started appearing.
Great catch by Craig. The root cause was a corrupted LiteDB file used by the UiPath Robot service for execution logs.
Execution.logDelete the contents of:
C:\Windows\System32\config\systemprofile\AppData\Local\UiPath\Logs\execution_log_data
Then:
When UiPath runs as a Windows Service, it uses the systemprofile directory instead of the logged-in user profile. If the internal LiteDB log database becomes corrupted, logs stay local and fail to sync to Orchestrator.
Useful troubleshooting point for anyone facing: