One of our customers experienced a malicious conversation. This exposed an unforeseen inefficiency in our database layer. A temporary fix was deployed within 90 minutes of incident discovery. The fix limited the speed of consuming events, in effect limiting the load on the database it caused. This stabilized the production systems. A long-term solution introduced a hard limit on conversation length. According to our analytics, no production bots should be affected by this limitation.