Scanning some messages causes Messaging Gateway to consume a large amount of cpu for a long period of time resulting in a failure to deliver the message and high cpu utilization while it was scanned.
Some messages with a specific malformity in their construction interacted poorly with one the Messaging Gateway filtering technologies resulting in unexpectedly long scan times.
This issue will be addressed with the next release.
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe
Thanks for your feedback. Let us know if you have additional comments below. (requires login)
This will clear the history and restart the chat.