Create assets with same name and different values when they are specific to robot


What is the use case

I have two VDIs which read the config file from a shared folder. When both VDIs try to access the file on a shared drive at a time it eventually causes one of the bots to fail.

How do you see a solution for the use case?

If I can create two assets with same name and different file paths(local drive paths) using per robot option bots can run individually without any conflict.


  • Assets
  • Automation Framework


Hi @rahamtullah,
If you create the asset per robot option, it should not conflict .Because you are configured the local path for the Robot.



Hi @balupad14

My bad… Thanks for correcting me.

I was trying to create a new asset altogether with the same name which confused me.