Building an Agent in Orchestrator facing an error

I am facing an issue “Foreground job requires an unattended robot to be defined on your user” i am trying to build a Agent in Orchestrator and used the RPA workflow as a tool when i am trying to run it is showing me the above error. I have community version of studio and orchestrator .. So run do i need to have any license or unattended bot setup?

Thankyou

@Snehamayi_Senapati

If your RPA workflow have froground activities like interacting with a desktop application or browser then, yes you will have to setup an unattended bot and assign it into the same folder where your agent is.

Thanks Ashok..

I donot have any enterprise license, i want to create a small demo using Agents in orchestrator so is it possible with studio user mode installation and orchestrator as community version.?

Thankyou for your help

Hi @Snehamayi_Senapati

Yes. Foreground jobs require an Unattended Robot. Even in Community edition, an Attended Robot alone is not enough. You must either configure an Unattended Robot, run it as an Attended job locally, or switch the process to run in background if possible.

@Snehamayi_Senapati

Yes, you can do that using community license. Here is a demo I had shared earlier.

1 Like

Hi @Snehamayi_Senapati ,

The error is because of the requirement of a unattended robot, In community edition you can setup a unattended license or you can assign a serverless instance and then you can attach to the right folder.

Hope this helps you

Regards,
Srini

Hi Team,

By going through one of the video i have assigned Unattended Robo account to my “Shared” Folder but my Process is always in Pending state as no other process is running i am facing this issue can anyone help me with this.
image

Thankyou so much Ashok for helping..

In Agentic Automation the zip folder contains .UIS file how to open that and use it.. The UiDemoTest workflow is working fine.

Could you please help me with the flow i need to add this in Agent Builder Tool

@Snehamayi_Senapati

Just publish the RPA workflow and use it as a tool in your agent builder.

yes but running the rpa workflow through Agent builder i am facing issue it is always in running state so i am not getting where i have done the mistake can you please help.

@Snehamayi_Senapati

is it in running or pending state?

cheers

It remains in pending state only

@Snehamayi_Senapati

then that means the machine is not available or there is no user account

if the assumption of license assigned is taken

cheers

Hi ,
These are machines

In the Shared Folder, I have assigned both the machine and the user, but the process is still in a pending state. Could you please let me know what else I need to check and where I should cross-verify? Is this happening because the currently installed version is showing an error? I need help urgently ..Thankyou

@Snehamayi_Senapati

open the machine that is connected and check if it shows connected in assitant and it is connected using client ID and srcret or machine key

if above is done as you are on community license the machine needs to be open for the automation to work…as in community unattended license is given but service mode installation is not possible

cheers

1 Like

Thankyou it worked i have connected through machine key..

1 Like

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