Orchestrator scheduled process execution was not ended

Hi Team,

We have some orchestrator schedule jobs for production run. I found robot executed the task without any error but robot process was not ended. Job showing as running state. Due to that other remaining schedule jobs were stuck.

I re-run the bot for same process without any code change and it gets completed with out any error. Job process also ended as normally.

Can you please help me on :

  1. Why the robot process was not ended ?
  2. How we can stop/ kill the existing running state processes after specific time interval ? So next schedule jobs can get executed.

Hello @Bhushan!

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:

  1. Always search first. It is the best way to quickly find your answer. Check out the image icon for that.
    Clicking the options button will let you set more specific topic search filters, i.e. only the ones with a solution.

  2. Topic that contains most common solutions with example project files can be found here.

  3. Read our official documentation where you can find a lot of information and instructions about each of our products:

  4. Watch the videos on our official YouTube channel for more visual tutorials.

  5. 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!

Cheers from your friendly

Hi @Bhushan,
It’s hard to tell without more details. Are you able to show the process and for example test it with debug option to see if it’s working properly etc.

Hi @Pablito

Yes, process is running fine in debug mode as well as run through orchestrator for other records. First time I was facing such scenario. I am using orchestrator version 2018.4.6.


I’m not sure but this might be related to old version of you Orchestrator. Maybe it’s kind of a bug which was in that version. To be 100% sure I suggest you to open ticket for Technical Support (as you are on enterprise plan).