We recently updated our Enterprise platform to version 21.4.3 and I’m having ongoing issues with running one of my processes.
At a glance, there are no validation errors and I’ve done just about everything I can think of/have read on the forums and nothing has helped me. This includes
Updating the JSON file manually (“studioVersion” was listed as 20.4.3 so I changed that to 21.4.3 and I also gave specific file paths for “entryPoint” and “main”)
Deleting the JSON and opening Main.xaml
Creating new projects from scratch and copying the contents of the process over
Updating any dependent packages
Creating/disabling, then re-enabling entry points/Main file
I’ve lost count of how many attempts this has taken me but for some reason I’m not seeing I keep getting this error when trying to run my process from the new Assistant.
Here are the raw error details
Entry point must be a file inside the current project. The used file was:
at UiPath.Executor.WorkflowLoader.LoadWorkflow(String workflowFile)
at UiPath.Executor.InProcessRunner.BeginExecute(AsyncCallback callback, Object state)
at UiPath.Core.Activities.ExecutorInvokeActivity.BeginExecute(AsyncCodeActivityContext context, AsyncCallback callback, Object state)
at System.Activities.AsyncCodeActivity.InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager)
at System.Activities.ActivityInstance.Execute(ActivityExecutor executor, BookmarkManager bookmarkManager)
at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation)
Luckily I am still able to run this process through Studio but I would like to get this person back on running it through Assistant. This was a rebuild of an older process and I’ve not been able to deliver for this one reason so any help is appreciated.
EDIT: I did attempt to regenerate the project.json and republish the process after doing so but that also did not solve the issue.
It seems that you have trouble getting an answer to your question in the first 24 hours.
Let us give you a few hints and helpful links.
First, make sure you browsed through our Forum FAQ Beginner’s Guide. It will teach you what should be included in your topic.
You can check out some of our resources directly, see below:
Always search first. It is the best way to quickly find your answer. Check out the icon for that.
Clicking the options button will let you set more specific topic search filters, i.e. only the ones with a solution.
Topic that contains most common solutions with example project files can be found here.
Read our official documentation where you can find a lot of information and instructions about each of our products:
Meet us and our users on our Community Slack and ask your question there.
Hopefully this will let you easily find the solution/information you need. Once you have it, we would be happy if you could share your findings here and mark it as a solution. This will help other users find it in the future.
Thank you for helping us build our UiPath Community!
I have the same issue. You are probably referring to a xaml that is not in your project. When I copy the xaml in the flow and reassign the invoke it works fine. I think it is a bug in the new update.
I had already contacted and met with tech support, I provided him with the latest NuGet package of this process and he told me that his team would take a look and that’s where we left things.
I’ve confirmed this to not be the case. This particular process invokes 2 different xaml files that are stored in the project folder. At that point, I wouldn’t expect the error message to look like this or at the very least there be validation errors when publishing.
@Kyle_Shahenian and @Dion I’ve reproduced this when using absolute paths within the Invoke Workflow. They execute fine in Studio but the Robot assumes they are in a relative path.
The easy fix is:
Open the Process from the nuget package
Delete the Invoke
Drag and drop the Xaml file from the Project pane
This should add the relative path
Publish
When publishing the Invoked Xaml files should be included in the .nupkg anyway.
There are other processes that we’ve deployed that use absolute file paths and I’ve never seen this error before or any that would suggest absolute file paths were at fault, in fact, the inverse is the case. I was using relative file paths and began having issues once we published to Orchestrator then pushed out to Assistant so I switched to absolute file paths and it has worked fine for quite some time.
Not eliminating other causes. This was what I had noticed from the process uploaded in our support ticket. If there are other causes I would love to have a look at them. Please schedule a call with our support reps and I will gladly join.
I was able to meet with the support reps on multiple occasions and after exhausting every measure we could think of, the process finally started running from Assistant. I know everyone is waiting for this epic conclusion so here it goes.
Basically @Constantin.Negrut was right on the money with his absolute vs relative file paths. The support rep I spoke with suggested the same thing and even though I use absolute file paths in literally every other process, I decided to try it for this one and it ended up running from Assistant the way it should. Marking it as the solution.
