Share
Report
123Hi, I am having odd behavior (in my opinion) for Machine groups running unattended desktop flows. We are having pool of VM's machines in Azure running specific desktops workloads. For example 2 groups, one group is running invoice processing, another are using for sales workflow.
Idea is to have number of machines to scale up if required. If there are few invoices, we spin 2 machines and if number of invoices is large and we need process all during day we can start extra machines. So total gourp include let say 4 machines but we only need use 2 or 1 only in average days. In general we can run all invoices during day with only 2 machines. During some peak time we will need all 4 machines running.
For some reason, if there only let say 2 machines running from 3 in group, few first desktops flows will go though and then it will stuck in queue forever until they timed out (in 3 hour) even there are VM's connected and available. All Desktop flows triggered from SharePoint list and use inputs variables from list. All flows request will start queued until I will start all machines in group.
Any ideas why this happened and is it normal behavior for machine groups?
All responses (
Answers (
