16-05-18 09:38 PM
10-08-23 03:15 PM
@AmiBarrett: Thank you for the hint! The Login works for me. However, how does your Schedule look like? My schedule ist Login-process-logout (running time > 2 min) and runs every minute. I have 2 ressources in my pool. The scheduler always starts only on one of the machines. The next schedule doesnt start after a minute but waits until previous schedule has finished.
Do I need 2 Logins,processes,logouts for 2 Resources in the scheduler?
10-08-23 03:25 PM
It's been a few years since then, and I've since changed employers. In that particular deployment, my team had actually written our own controller in C# to replace the one provided by Blue Prism, which got around some of the limitations of the 5.x platform that were present at the time (this being one of them).
Your order of tasks within a schedule looks correct, and the scheduler shouldn't be aware of which account is being supplied to Login Agent on that level. In theory, as long as it's a pool, it should allow you to execute the same process/schedule twice. If it's still causing problems, you might try experimenting with an active queue against your pool.
11-08-23 10:02 AM
Thank you for the reply Ami!!
Active queues doesnt fit our use case. However, I am playing around with environment locks so that the pool is able to check if a resource is available. I plan to run two separate schedules on the pool with a little time in between.
Will keep you updated 🙂
a week ago
Hello @TomCirone
I believe we have solved your original request with Automation Orchestrator (powered by Next Gen) and the recent additions of Dynamic Worker allocation with process chaining.
I appreciate this question was raised a long time ago. It is one of the multiple customer points of feedback which led us to deliver Automation Orchestrator (powered by Next Gen). Our latest enhancements include Automation Flows, Dynamic Worker allocation, Process Chaining, Digital Worker Groups, and Triggers, which provide flexibility, efficiency, and control over automation processes. These capabilities are available to our Blue Prism Enterprise customers with Automation Orchestrator (powered by Next Gen).
Our Automation Flows (which supersede schedules) allows you to create sequences of automations that can be executed in a specific order, and separately define multiple triggers, including Work Queue triggers and time-based triggers. We have clash detection built-in, so that if a digital worker is busy, the next session (process run) would be queued, ready for when a worker becomes available, giving you greater resilience and utilization.
Our Digital Worker Capability Groups (which supersede Resource Pools) enables customers to define and manage groups of digital workers with specific capabilities, ensuring that automations are executed by the most suitable workers.
In addition, our Process Chaining capability enables customers to create sequences of automations that can be executed in a specific order, including login and logout steps.
This allows for more efficient and streamlined automation workflows because a chain can be assigned to any worker within a customized capability group.
To learn more about Automation Orchestrator (powered by Next Gen) and how it can help your organization streamline and optimize your automation workflows, please visit our online documentation portal at https://docs.blueprism.com/en-US/bundle/next-generation/page/automation-orchestrator.htm.
Related ideas where I've shared the same update:
I am really excited to see the impact that these capabilities will have on our customers' automation initiatives and look forward to continuing to innovate and deliver value to our community.
Kind regards
Chris Strong
SS&C Blue Prism – Senior Product Manager (Next Gen RPA)