Elastic Robot Orchestration - Automatically Create Machines

[alejandro.soguero (Alejandro Felipe Soguero)]

Hi all,

After configuring an Azure elastic resource pool within my Orchestrator following Elastic robot orchestration

I would like to know how to specify in UiPath the requirements to create or delete VMs within that resource pool.

According to the official documents (Automatically Create Machines): UiPath creates as many machines as needed to optimally handle the workload, within parameters you set.

• What are these parameters? Are them related to any SLA?

Currently my Azure Elastic Pool is working with only 1 VM. I’m triggering a lot of parallel executions in this Elastic Pool but all of the executions remain queued to be executed in the same VM, I want UiPath to create additional VMs to handle these parallel execution and reduce overall execution time.

Thanks for your help

Best regards,

[Anil_G (Anil Gorthi)]

@alejandro.soguero

Welcome to the community

I guess you need to create the VM Image first as required for auto scaling

Elastic robot orchestration

Here you can see the parameters for configuring the auto scaling

Elastic robot orchestration

cheers

[ABHIMANYU_THITE1 (ABHIMANYU THITE)]

Thanks for sharing @Anil_G !

[alejandro.soguero (Alejandro Felipe Soguero)]

Hi @Anil_G,

Thanks for your response, I forgot to mention that I’m already using a VM image for auto scaling and I’ve tried to configure the Elastic Pool with all the different profiles.

Using the advanced profile, I’ve set 2 Standby Machines and 10 min Idle Machine Timeout. I’ve launched several tasks to that Elastic Pool and all of them remain pending, do you know why UiPath is not creating at least 2 VMs to handle the executions?

Thanks!