Unable start a Job using Orchestrator on my Local Machine

@Prabu_visu I’m facing same problem did u find solution

@vivek_k what Robot and Orchestrator version?

im using community edition it was working fine from today only im facing this issue when ever i tried to run its just throwing me execution is cancelled sometimes before execution sometimes after a few seconds , when i tried to run it from orchestrator the status remains pending @ovi @sreenivasm

Hi, i have just reinstalled the application issue is resolved

1 Like

:+1:

Hi! I am facing the same problem … Did you reinstall Community Studio?

nope @carmen for one use case it worked fine thn again im facing the same prblm reinstalling also does not sole the issue

I just read that they are facing some problems … we will need to wait I guess…

@carmen do you still have the issue with job not starting? Did you try with multiple processes?

@ovi yes, well I am just trying a sample project …just learning now how to use orchestrator and says pending when I want to execute …and today I tried to do with a coworker and happen the same …and we run from UiRobot and the process stop unexpected. I think that is a orchestrator issue because if we run locally runs ok.

Do you have any errors?

@ovi no errors

That’s odd. Just tried and worked on my side. I’ll let our team know to investigate. We did some improvements to fix the latest issues. And on Sunday we have scheduled an infrastructure upgrade: Orchestrator CE - Scheduled Maintenance Downtime

I have the same problem! I hope a resolution soon :confused:

Even I have the same Issue. From Agent it works fine but not with a Manul running from Orchestrator

I can start jobs from orchestrator CE no problem just a few hours…

1 Like

@dlucas85 and @Ganesh_Hegde,

This is known issue follow the below steps and you will be able to run the jobs

The job goes in pending state because while provisioning the robot you would have given only username, you have to give Domain\username.

You can get the domain information through command prompt

whoami or set user

If this part is done, then you can refer the above post.

Please refer the below post

Using CE with a two robots but one robot is acting weird RPA Developers

Hi @soneill437, The job goes in pending state because while provisioning the robot you would have given only username, you have to give Domain\username. You can get the domain information through command prompt whoami or set user Refer the below post.

6 Likes

Thanks I have tried this and my issue has been solved.

1 Like

Thank you. The problem is resolved for me too by applying the above solution.

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