I am encountering an intermittent issue where UiPath.Executor.exe crashes completely during the execution of a process. Based on my investigation, this seems to occur when the bot is trying to execute a Get Asset activity.
Instead of throwing a catchable UiPath exception, the process terminates abruptly with a standard Windows “UiPath Executor has stopped working” dialog. When I checked the Windows Event Viewer, I found an Application Error (Event ID 1000) and a .NET Runtime Error (Event ID 1026).
Environment:
UiPath Studio / Executor Version: 2025.10.7 (on the bot runner machine)
Here is the stack trace from the Event Viewer:
Application: UiPath.Executor.exe
CoreCLR Version: 8.0.1525.16413
.NET Version: 8.0.15
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ArgumentNullException: Value cannot be null. (Parameter ‘source’)
at System.Linq.ThrowHelper.ThrowArgumentNullException(ExceptionArgument argument)
at System.Linq.Enumerable.Where[TSource](IEnumerable1 source, Func2 predicate)
at UiPath.OrchestratorClient.Utilities.AssetCacheManager.CacheAssetToFile()
at UiPath.OrchestratorClient.Utilities.AssetCacheManager.<>c.<.ctor>b__14_0(Object sender, EventArgs e)
Context & What I’ve tried:
The target Asset does exist and contains a valid value in Orchestrator. It is not actually null.
The bot runs perfectly fine most of the time; this crash happens randomly.
I have already tried clearing the local UiPath cache, but the issue eventually returns.
Note: I am aware that a highly similar issue occurred in older versions (e.g., UiPath.System.Activities 2022.10.3), where downgrading was the suggested workaround. However, I am looking for a long-term solution or troubleshooting steps without having to downgrade my current packages or Studio version.
My Questions:
Is it possible that this is a regression bug specifically in the 2025.10.7 version affecting AssetCacheManager.CacheAssetToFile()?
Could this be related to a micro-drop in the network connection between the bot machine and Orchestrator precisely during the caching phase? If so, how can I properly investigate and verify if it’s a network issue versus a local environment issue (e.g., Antivirus locking the cache file)?
Are there any specific diagnostic logs or configurations I should check to pinpoint the exact root cause?
Any guidance on how to deep-dive into this would be greatly appreciated. Thank you!
This might be a regression pattern in newer builds when AssetCacheManager hits a null source during cache write. It is usually triggered by a brief network drop or a locked cache file. Check Windows Event Viewer, UiPath Robot logs (Execution and OrchestratorClient logs), and antivirus exclusions for the Robot cache folder. If the issue persists, raise a UiPath support ticket with logs because this version likely has an intermittent Asset caching bug.
If helpful, mark as solution. Happy automation with UiPath
Hi @chinthakayala_karthik, I checked the Event Viewer and found Event ID 1026 (ArgumentNullException at CacheAssetToFile). If I run the Diagnostic Tool, what exactly should I be looking for in the results?
Thanks @ppr I usually use a Retry Scope for network delays too. But in this case, the ArgumentNullException instantly crashes the entire UiPath.Executor.exe process. If the whole application shuts down abruptly, would a Retry Scope even be able to catch it and run again?
@Raluca_Laic I apologize, but it seems I don’t have the permission to send a Private Message directly to you (the Message button is missing on my end).
Could you please initiate a Private Message with me first? Once you message me, I will reply and attach the Diagnostics tool .zip file and Event Viewer logs immediately. Thank you.
The issue is caused by a known bug in older UiPath.System.Activities versions (<22.10.5) related to asset cache cleanup. Here is a quick breakdown of the issue and how to fix it:
The Cause: When a process using Get Asset / Get Credential finishes, the cleanup routine may try to save cache data even when nothing was cached, throwing an unhandled exception.
The Behavior: This occurs during executor cleanup rather than workflow execution. This is why it can appear randomly, even while other processes are running.
Why Re-running Works: The issue is a transient state, not persistent data corruption, so a simple re-run usually bypasses the error.
The Solution: Updating all processes to System.Activities 22.10.5+ (preferably 23.4.x or later) will permanently resolve the issue.