I have developed a process which I have tested successfully in Studio with predefined arguments. I have then published the process to Orchestrator and want to run the job from orchestrator on an unattended bot.
I have adjusted the arguments in Orchestrator for the process but when I execute the job there seems to be a weird issue.
Example:
Process should execute a delete folder activity.
I get error log message that indicates that the folderpath is stitched together by a local folderpath from the nuget package (path to the content folder in the nuget package) and the actual folderpath from the argument.
I have never experienced that issue. Is that a publishing error? How can I solve it?
That’s a code error. You have likely specified a filename without a path, which is when it will stitch the current running folder to it. Or you’ve misused Environment.CurrentDirectory or somthing like .\FolderName - You should always use complete explicit paths, because things change when you are running unattended - the Environment.CurrentDirectory ends up being the folder where the robot stores the .nupkg file. You should never use folders within your project to store files as the process runs. You should always use external folders such as the Downloads folder or a network share.
I noticed that too that I used the temp folder within the project folder while developing (usually I never do that but this time it happened that way). But when I change it to an external folder it kind of remembers the internal folder…
It may be the case that it’s value is still there in the project at another location/scope?
May be search for that path you had provided initially in the project by using ctrl+f, it may show other instances of that path defined in the project.
I found my stupid error. I entered the argument values with " " around them. That way Orchestrator adds a " \ " at the beginning which indicates an indirect path.