@sushmam9 Your bots really don't have a limit to the number of automations they can contain in total. Robot Manager will only assign work one at a time (which is generally necessary for robotic process since they use applications designed for humans). Best practice is that you limit your bots to only related processes to avoid excess testing and maintenance problems. If you have a bot that can do ten different processes, then anytime one of those processes change, you would need to update your bot to handle it. The other nine processes did not change, but you'll likely need to re-test them since you are changing the bot itself and have a slight risk of causing damage to them when making any change.
One option you can think about is building your processes using Pega cases and execute specific bot steps against your applications to retrieve data from and/or update the applications. You might have a bot process to add a note to a given application, or one to retrieve account data from an application. These might be different work queues but would use the same workgroup (bot). The Pega Case would be used to execute the various bot steps and assemble those into the proper output.
My suggestion is to make your bots as lean as possible so that you can easily change and maintain them. If you are using auto-balancing and prioritizing your work, then you can have as many bots as you need doing disparate things and still complete the work.