I've noticed that if you have an app that sends a large quantity of messages to a space in a short amount of time, you can make the callback "lag" while WW tries to process all the messages.
For example, my app sent 26 messages in the span of about a second, and it took 22 minutes to fully process those. In the meantime, any command sent to the app appeared to be ignored.
I tried reproducing this by manually entering messages as fast as I could, but the messages all got handled virtually instantly.
Obviously, having that many messages spammed at one time is not a normal use case, but it's a possibility for apps - we might want to mention a recommended limit of, say, 2 messages per second or whatever is considered reasonable. The other concern, perhaps not valid, would be inviting a malicious app into the channel, which could spam a couple thousand messages at one time. Not sure how that would be handled (and not anxious to try and find out lol)
Please sign in to leave a comment.