Multibot in Appian RPA

I should've been more clear about the question: is Appian RPA a real multibot technology?

Appian RPA can successfully and smoothly handle hundreds of simultaneous RPA Agents online with thousands of simultaneous executions. There is no direct 1-1 comparison between how UiPath manage queues because UiPath cannot be compared (only) with Appian RPA; you have to leverage all Appian platform capabilities. The best option is using the Process Model as the dispatcher.

miguelangel.carnero - after a year or so with the product: by default the product is not able to process concurrent transactions, one "runner" is not able to lock one transaction in order to stop another "runner" to access it. Again, I'm talking about "by default". Show me proof that I'm not correct and I will change my opinion.  

nicolaem159908  Thanks for your feedback. I would really like to understand your point to try to help explain how Appian RPA address this. If I may, I have some questions and comments:

Questions:
Q1. What do you mean by "The Product"? Appian RPA, Appian platform, both?
Q2. What do you mean by "default"? Asking because, if I am not misunderstanding your need, that can be easily addressed with Appian and Appian RPA OOTB capabilities.
Q3. What do you mean by "a runner"? Asking to clarify to what you are comparing it with in the Appian platform. Same needs are normally addressed differently between vendors. That does not mean it cannot be addressed, just the way to do it is different.
Q4. Could you provide a specific, detailed description of the use case you're trying to address with Appian and/or Appian RPA?

Comments:
- "Concurrent transactions" is one of the most common use cases and it is extremely easy to address with Appian RPA by configuring the number of Agents you need and the proper Robot Pool to manage it. Then, Process Models can add additional orchestrator logic when necessary.
- Comparing concepts between vendors often lead to confusion. We recommend trying to address the use case with Appian from an holistic perspective, using all its platform potential, without making 1:1 comparisons.

nicolaem159908  Thanks for your feedback. I would really like to understand your point to try to help explain how Appian RPA address this. If I may, I have some questions and comments:

Questions:
Q1. What do you mean by "The Product"? Appian RPA, Appian platform, both?
Q2. What do you mean by "default"? Asking because, if I am not misunderstanding your need, that can be easily addressed with Appian and Appian RPA OOTB capabilities.
Q3. What do you mean by "a runner"? Asking to clarify to what you are comparing it with in the Appian platform. Same needs are normally addressed differently between vendors. That does not mean it cannot be addressed, just the way to do it is different.
Q4. Could you provide a specific, detailed description of the use case you're trying to address with Appian and/or Appian RPA?

Comments:
- "Concurrent transactions" is one of the most common use cases and it is extremely easy to address with Appian RPA by configuring the number of Agents you need and the proper Robot Pool to manage it. Then, Process Models can add additional orchestrator logic when necessary.
- Comparing concepts between vendors often lead to confusion. We recommend trying to address the use case with Appian from an holistic perspective, using all its platform potential, without making 1:1 comparisons.