We have had a few instances where after a collect connection issue many thousands or rows are created for failure e-mails to be sent. The Worksflow send message service does not complete before the next execution. These seem to cause contention and quickly the service queue is filled with 12 (or what ever the set up is) of the same service task all of which do not complete.
Is it possible for these potentially long running service tasks to check to see if one is already queued/running and only submit if the answer to this is NO?
Tim, makes sense to me. I will add this for discussion with the framework engineering team to get there take on this requirement.
Attachments Open full size
This is the same as that below which is planned. - Thanks
Attachments Open full size