This is because, you can’t access local file from web studio until and unless you upload it somewhere like storege bucket or one drive or share drive and then before reading you will have to download from the source into bot memory or runtime memory. Once the file will be there in the memory, it will be read by bot.
It’s architecture is different than the studio desktop where everything locally will be accessible by the bot. For studio web you will have to write the logic to make that local file available to the bot.
Hi @tyagis,
Studio Web projects run on cloud-hosted (serverless) robots by default. When you hit Debug, the execution happens in a container in UiPath’s cloud, not on your machine, so a path like what you’ve provided in your flow simply doesn’t exist in that environment.
That’s exactly why your Read Range Workbook failed with “workbook does not exist”, the file lives on your local disk, but the robot executing the workflow is looking for it in the cloud sandbox.
However, you can change your setup to local from here:
Studio Web supports a “local setup” mode where you install a local runtime/connector so debugging happens on your own machine instead of the cloud.
Then, run the workflow locally to access files in your local folders. Note: this is only a debug-time fix, publishing and running it on another machine or server will hit the same “file not found” issue, since that local path won’t exist there.
Happy Automation!
