Sometimes – regardless of how advanced our software, hardware and networks become – it’s the simplest of problems that give us the biggest headaches.
That was the case for a few of our customers recently. After taking the time to build, test and deploy their interfaces, they were faced with a situation they hadn’t prepared for: What to do when duplicate messages were sent to one of their channels?
This may not seem like a huge issue when a message is accidentally sent twice – but imagine what would happen if, like a broken record, that same message was sent 100, 1000 or even 1,000,000 times. That’s a lot of needless stress to place on your database when all you’d be doing is updating an identical record.












