At one of my customer, I have seen some circumstances where the Workflow Subscriber was not able to process/analyse all MSQ messages in the queue in a timely manner.
I would like to know what is the proper way to configure the WF subscriber to process more in realtime. Is there a configuration (like for the number of tasks per CPU for WF service) that we can modify to increase Subscriber analysis capabilities?
Also, I have seen a situation where one Workflow did trigger and started modifying a document in loops. It took one day for the customer to notify us and discover the source. By that time, that document got modified too many times and this causes the MS Queuing service to have over 1 000 000 million notification in the queue. It took two days for the WF Subscriber service to process them all (even if that document modification was not triggering any Workflow) and allow regular Workflows to start processing normally.
In order to prevent such situation, is there a way to modify the Workflow engine to monitor the size of the MSQ and if it gets higher than a specific number, then the WF service can send an email notification to the Laserfiche administrator?