Asset File Path on Shared Drive Works in One Process but Not Another

Help Orchestrator
1

Hi UI Path Community,

I have a process that references an asset file path located on a shared drive, and it functions correctly without any issues.

However, I have another process that also references an asset file path on the same shared drive, yet this one is not working as expected.

Could anyone help me understand why this discrepancy might be occurring, and what I should check to resolve it?

Any guidance would be greatly appreciated. Thank you in advance.

There is no error or the job is not faulted. It just does not logged on the file path.

2

Please explain what you mean by this. Are you modifying the file or just reading it? Also what is expected behaviour?

3

I am modifying the file and the expected behavior is that it must get the Value of the assets file location. It works on the Dev machine but in the prod it does not work

4

@Nahte_16

Ok. You can check the assets being initialized have the expected value and also the activity which you are using to modify file is using the asset.

You can log the asset value before being used so you will get to know what file path it’s using in dev and prod as well.

5

Hi @Nahte_16,

Verify whether the absolute path in the Asset is exactly the same in the target environment (e.g., Prod vs Test). A small difference in the mapped drive, UNC path, folder name, or environment-specific configuration could cause the robot to point to a different location.

Are you getting any error message?

Thanks

6

No, I don’t get any error messages however I log the asset value and it returned as False whenever I am on the Prod machine. But in the Dev machine it works completely fine

7

The issue could be related to the drive mapping. Could you check whether the drive letter or path is the same on the Prod machine? If you can’t access the prod server then need to check with your support team.

8

Yes, I also checked it, it is the same as the dev and prod

9

Can you check robot account has the required read/write access to this specific folder on the shared drive.

10

Thank you!

I already checked it and it has the right for read/write access. However I still facing the same result.

11

Thank you for the replies.

This issue has been resolved.

What we did was change the requiresUserInteraction to true on the project.json file now it works.

12

Ok so you had background process initially and then you changed it to foreground.