All of my automations begin with using the Get Asset Activity to grab a config file. All of these automations that I have running have been successful for 12 + months with no issues. Lately, I’ve been getting an error popping up with this activity: Object reference not set to an instance of an object and I’m confused as to why I’m getting this. I would assume if I’m getting this error that I should get it every time, but I don’t. And, it doesn’t just happen with one automation, it will randomly occur in multiple. Then, I won’t have the error for a week or 2 and then it will return randomly. I’m using Cloud Orchestrator. Can someone possibly help me understand why I may be getting this error for this activity and why it’s random? The location of the config files haven’t changed. Below is an example of what I get.
try to check the event viewer logs with the timestamp and check the error there it might give the issue
mostly you might be selecting the or giving the variable name directly..if you try to edit the process in process tab in orchstartor and check if the resources are mapped…
But the issue might eb related to orchestrotor errors ..thsi can be confirmed from event viewer if orchestartor rejected the call..if you surroundinf with retry scope with a small delay can help here
cheers
@Anil_G,
Thanks for the help pinpointing issue.
Found it. Event Viewer shows my VDI lost connection to two different cloud endpoints within 12 seconds — Nexthink Collector at 3:36:36 (websocket closed by remote host) and then UiPath couldn’t reach UiPath for the OAuth token at 3:36:48 (UnauthorizedAccessException → NullReference). So it’s a transient network drop on the VDI, not Orchestrator rejecting the call and not a Studio config issue. Going to wrap Get Asset in a Retry Scope as you suggested.
