Description

When uploading a bot to Orchestrator using files existing on a machine, the paths to these files cannot be relative paths. Otherwise, when Bot Runner runs a bot, it looks for files in locations impossible to access from that device. 

In this article, you will learn how to run workflows from different a machine when they need to interact with files locally saved.

Notice that you can also use these instructions if you face a "File not found" error message in the logs.

Instructions

To ensure that bots run as expected, always use full paths to any needed files. This works for normal paths or UNC paths as long as they are full paths and not relative ones. Here's what we need to do:

1. When using an activity, into the "Directory path", click "Set value" and then enter the full directory path as shown in the following screenshot.

2. Another option is to select the UNC path as in the image below.

 

Note: If the file path is entered only with the file name, the Bot Runner will look for this file in the directory where Bot Runner is installed. Look at this example:

 

Related articles

Any activities that reference a file path would need to be set up in this manner. This includes, for example, Excel Activities and OS Automation Activities.