How does the Superbot dynamically reallocate itself to cater to high-priority profiles?
In organizations with multiple robots, there is a possibility that requests in high priority profiles do not get executed within defined SLAs while certain robots are working on non-priority tasks. The average time per task could vary based on system performance, flow complexity and other parameters. Robot that is marked as Superbot dynamically reallocates itself to cater to high-priority profiles as per the reallocation criterion.
The Super Bot has the capability to reallocate base on three scenarios -
- Queued Requests Volume
- Request Expiry Prediction
- SLA Scaling Prediction
To understand it further, you can refer the below knowledge base URL -
Thanks for the quick answer and the link is useful.