The RabbitMQConnector works great and can be hosted as a Stream from Flow/Server. While we do not have any technical issues with that deployment, it does require a dedicated engine. So, whenever we need to build a new RabbitMQ listener (and this would be true for other messaging platforms as well) we need to license a new engine even if we don’t really need a dedicated one.
Launching through an automation trigger we could just process the message on any available engine but not tie it up indefinitely.
Thanks for the consideration.
