Orchestrator Execution Fails with “Your UI Connection could not be found” — Works Fine in Studio Web

Help Studio Web
, ,
1

Hi everyone,

I’m currently working with UiPath Studio Web, and I was able to successfully run my automation from Studio Web itself. However, when I tried to execute the same automation from Orchestrator (via a trigger), I encountered the following error:

Your UI Connection could not be found. Please recreate or edit it and retry. UiPath.UIAutomationNext.Exceptions.OrchestratorNotFoundException: Your UI Connection could not be found. Please recreate or edit it and retry. at UiPath.UIAutomationNext.Orchestrator.Rest.HttpResponseMessageExtensions.EnsureSuccessStatusCodeAsync(HttpResponseMessage response) at UiPath.UIAutomationNext.Orchestrator.Rest.OrchestratorService.DoRequestInternal(RetryAuthorizationHttpRequestMessage request, CancellationToken cancellationToken) at UiPath.UIAutomationNext.Orchestrator.Rest.OrchestratorService.DoRequestAsync(OrchestratorRequest orchestratorRequest, CancellationToken cancellationToken) at UiPath.UIAutomationNext.Orchestrator.OrchestratorSystemBucketsService.DownloadFileAsStreamAsync(String bucket, String fileName, CancellationToken cancellationToken) at UiPath.UIAutomationNext.Orchestrator.OrchestratorSystemBucketsService.DownloadFileAsync(String bucket, String fileName, Stream destination, CancellationToken cancellationToken) at UiPath.UIAutomationNext.Services.UserData.UserDataConnectionService.RestoreUserDataFolderAsync(UserDataConnectionRestoreRequest restoreRequest, CancellationToken cancellationToken) at UiPath.UIAutomationNext.Activities.NApplicationCard.RestoreUserDataFolderIfNeeded(ITargetApp targetApp, String connectionId, OrchestratorContext orchestratorContext) at UiPath.UIAutomationNext.Activities.NApplicationCard.GetMainWindowByTargetApp(IActivityContextWrapper context, ITargetApp targetApp, CancellationToken cancellationToken) at UiPath.UIAutomationNext.Activities.NApplicationCard.GetRuntimeData(IActivityContextWrapper context, CancellationToken cancellationToken) at UiPath.UIAutomationNext.Activities.NApplicationCard.OpenOrAttach(IActivityContextWrapper context, CancellationToken cancellationToken) at UiPath.UIAutomationNext.Activities.NApplicationCard.ExecuteAsync(NativeActivityContext context, CancellationToken cancellationToken) at UiPath.Shared.Activities.AsyncTaskNativeImplementation.BookmarkResumptionCallback(NativeActivityContext context, Object value) at UiPath.Shared.Activities.AsyncTaskNativeActivity.BookmarkResumptionCallback(NativeActivityContext context, Bookmark bookmark, Object value) at UiPath.Shared.Activities.ContinuableAsyncNativeActivity.BookmarkResumptionCallback(NativeActivityContext context, Bookmark bookmark, Object value) at System.Activities.Runtime.BookmarkWorkItem.Execute(ActivityExecutor executor, BookmarkManager bookmarkManager)

From what I understand, the automation is using a UI Connection that works fine with the serverless robot triggered by Studio Web, but it seems to fail when executed by the robot through Orchestrator.

Could anyone please advise:

  • Why this UI Connection error occurs only in Orchestrator?
  • How can I make sure the correct UI Connection is available when running from Orchestrator?
  • Are there differences in how UI Connections are handled between serverless robots and Unattended robots?

Any insights or examples would be greatly appreciated.
Thanks in advance!

2

Hi @mkt.scott4

As per your message you are using server less cloud robot. I hope you have followed below before running from orchestrator.

How to Use Serverless Robots:
Process Design: Ensure the process you are trying to execute was designed as a background, cross-platform automation.
Robot Units: You need to have available robot units (RUs) for the tenant in which the process needs to run.
Orchestrator: Manage serverless robots and their executions through the UiPath Orchestrator.
Executing Unattended Automations: You can launch unattended jobs manually from the Jobs page or automatically triggered in a pre-planned manner via triggers.

Did you also tried with un attended automation fir the process you deployed from studio web.

Regards,
Kirankumar.

3

@mkt.scott4

Is it being executed on a server or a serverless cloud robot?

Cheers

4

Issue resolved!

As mentioned, the process needs to be designed as a background, cross-platform automation.

“Process Design: Ensure the process you are trying to execute was designed as a background, cross-platform automation.”

And it’s clearly stated in the documentation as well:

“A background, cross-platform automation project that has been published to Orchestrator and added to your folders.”

Thank you!
I was indeed trying to run a foreground process using a serverless robot — that was the issue.

1 Like
5

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.