Trying to understand Orphaned Messages
We are constantly running into issues where there are billions of Orphaned messages in our system that cause problems, and we have to manually run a cleanup to fix performance issues.
In the following article about orphaned messages... https://community.intersystems.com/post/ensemble-orphaned-messages it mentions either programmatically eliminating the Orphaned messages or using a Utility like Demo.Util.CleanupSet in ENSDEMO.
I have had it explained to me is basically all messages have to go somewhere, if they aren't then it creates orphaned messages.
So how should I go about getting rid of the problematic code that is causing the Orphaned messages either in a Business Router, or a Business Process?
Is there a way we can automate the cleanup process in the Task scheduler to run every so often so we don't have to run it manually? Does anyone have some helpful hints or suggestions to go about doing this? I understand the code, just the implementation of how to do it is what I am having problems with.