Robot not visible in 'start job' in Orchestrator

Help
1

Slightly different to other posts with similar titles.
I’ve just started playing with Orchestrator for the first time (Community Edition).
I have Studio installed on an AWS Workspace. I have connected the bot and it is showing a green tick - connected and licensed. The process is showing as available and I can run it from the robot tray.
I have one bot of type attended in an environment called ‘MyEnvironment’
I have a process called Test in MyEnvironment.
When I run the process from the robot tray, orchestrator tracks the process and logs completion.
The bot shows as available in orchestrator
But it still does not appear to assign jobs.
I’m probably overlooking something obvious, but for the life of me I can’t figure out what it is :slight_smile:

2

Hi @JohnMac

Have you assign the process to the bot?

Thanks
Ashwin.S

3

I have assigned the process to an environment, and the bot is in that environment. I cannot assign the process to the bot in the start job window because it does not appear as an execution target. I’ve attached a compilation of screenshots if that helps.

image
image647×748 51.6 KB

image
image
image1419×156 12.4 KB

4

Hi @JohnMac

Check this
Robot Not Visible To Start Job In Orchestrator

Thanks
Ashwin.S

5

Hi all,
I ended up republishing the process with a different name, which seemed to resolve the issue. Not sure what the underlying cause was - possibly calling a process ‘Test’ was a bad idea as that term may be used for something else. Anyway - ‘Test2’ worked perfectly.
J

6

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