We took the plunge and will update this topic once it has been running for a while.
Hi Steve. Due to our large user base, we are currently running eight (8) action processors in our environment. However, all eight instances are running the same AP rules.
Hi Steve, for having a better retry-control and better performance, we are using a own written Job-Processor. Its Action-based an simple to hande. We can descide, which jobType should run on which action and give each JobType (like Smartmail, logAction, Interface, what ever...) a dedicated “action Processor”. And for each of that, we are able to have “next try”-Options (in case, that a SMTP-Sever has no connection etc.) - reacting on the specific reply.