Schedule sequence of processes

i_planned
orchestrator

#1

We would like to schedule a sequence of processes

  • Start process A on Robot X OR Y OR Z
  • When finished start process B on Robot X AND Y AND Z
  • When finished start process C on Robot X OR Y OR Z

E.g. we would like to finish an ADD_Queue_Process on one robot before we start Process_Queue on all avaiable robots
We do not know how long add queue will take.
We don’t like to start process queue before add queue process is finished.


#2

We’ll implement. Of course till then you have an workaround.

  • Schedule Process A at 12:00
  • Schedule Process B at 12:01

Process B will be queued.


#3

Thanks Badita,

workaround does not work if Process B should run on more robots than Process A but it is important that A is finished before B should start.


#4

Is this still going to be implemented? It’s pretty simple in Blue Prism to have process A run on one bot (Bot A) then have process B start running on other bots (Bot B, Bot C).


#5

Any help or lead… I too have the same scenario…
We would like to schedule a sequence of processes

  • Start process A on Robot X OR Y OR Z
  • When finished start process B on Robot X AND Y AND Z
  • When finished start process C on Robot X OR Y OR Z

E.g. we would like to finish an ADD_Queue_Process on one robot before we start Process_Queue on all avaiable robots
We do not know how long add queue will take.
We don’t like to start process queue before add queue process is finished.


#6

Why can’t you run process_queue in parallel with add_to_queue. Any specific reasons?


#7

Say Process A (Load Queue - runs in Single machine )
Process B (Preform the actual processing in the Application using Input Queue, runs on multiple machine to handle the load)
Process C( once all Queue data are Processed, prepare and send report, runs on single machine because we want to send report only once )

Can you please tell the solution for the above scenario


#8

I like this idea. We do this currently by coming up with schedules close to correct, and then with some set/get assets and come checks on the queue.

e.g. in your scenario, option 1:
Process A Runs, and then at completion of the loading sets an asset called “Load_Complete” to true.
Process B is scheduled on multiple bots, and at the start just does a get asset of “Load_Complete” and it isn’t true then it delays for a few minutes and checks again.
Process C Scheduled later, and it just checks that there are no queue items of type new, and no items in progress, again, just delaying and checking again if there are.

A modification as option 2, would be to have Process A use the start process activity to start process B on as many robots as needed. We have a process that works out how many bots it needs and starts that many dynamically.


#9

In the Option 2,if we use “Start job” activity, it has only number of Bots say 3,no option to select or choose that specific 3 bots. Is there a way to say run on specific bot using Start job.

I think you are referring “Start Process” activity instead of “Start job” activity, please correct me if I’m wrong.


#10

It is start job - https://activities.uipath.com/docs/start-job

Our solution for this is to have a second environment created with only the bots we want to run the job. You start the package as processname_environment.

So if you just put the three robots in that environment, and start three it’ll end up one each.


#11

Thank you David for quick reply,its is helpful. Creation of Environment is done only by dedicated Support group,they will not, as it increase the maintenance effort for them if number of automation’s increases.

Looking for other alternates, like using API or any other…


#12

That’s a shame. You can definitely start a job with the api, just not sure if you can target a specific robot.

It really isn’t any work for the support guys, it’s about a five second job to have another environment setup. It is just a config in orchestrator, it isn’t a totally seperate set of servers or anything. Robots can be in multiple environments.