Details
-
Task
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
Description
For a given bot name (UiPath orchestator: package), we fetch all known releases (UiPath Orchestrator: processes, i.e. combination of execution environment and package in a specific version) from UiPath and potentially start a job for every one of them.
This could lead to multiple issues, one of them being very complex error/success handling (i.e. When is the external task done? When all UiPath jobs are done? Is an external task failing if one of the jobs is failing?).
AT
- Ensure that for a given bot name we only start (at most) one job in UiPath.
- We have a documented strategy how we pick a release in case multiple releases share the same process key (e.g. latest version or random)
Hints
- We could keep the "get all releases and start jobs on them" mechanism but would have to choose one of them
- potential issue: we might always trigger the same process (i.e. environment) which is bad load balancing
- We could investigate if we could start a job with the given bot name (a.k.a package) only, supplying that we want to start only 1 job
- potential gain: let UiPath do the load balancing
- potential issue: might not be possible via their API
