12 ms·
It's not deleting prod, but this reminds me of a funny story when we kind of prevented a low-cost airline from being able to sell any tickets for 8~ hours. We
by squeaky-clean 3y ago
It's not deleting prod, but this reminds me of a funny story when we kind of prevented a low-cost airline from being able to sell any tickets for 8~ hours.
We ran the booking websites for lots of airlines (Which was really just a frontend that connected to Sabre or Amadeus). Airline data standards were bad. They're probably still bad. You were lucky if you could get an airline's upcoming schedule or pricing rules in some format other than "manually typed into an email by a human". We had people who's job was solely just to take these emails and put the info in the database.
We had a bunch of arbitrary safe-guards against data entry mistakes. Ticket prices above 10k or under 10 were flagged as suspicious and needed someone more senior to approve them.
So this airline, headquartered somewhere with a 7 hour time difference from us, wants to do a 9 euro flight special for some holiday. There's a big marketing campaign, apparently lots of excited customers, etc.
I don't know if you've connected the dots yet but 9 euros was less than our suspicious-data-threshold of 10. So about 95% of their available flights just disappeared. Searching for them would turn up a "no results" page. The only available flights were expensive ones excluded from the sale, usually codeshares with a larger airline for a more distant destination.
The airline never notified us. It wasn't until we waltzed into the office 7 hours later that any one of us saw the problem. One of the DBAs wrote a quick "approve all suspicious entries" query and that was the end of it. Thankfully it was a 3 day sale.
Afterwards, I remember the chosen method to prevent this from happening again was to change the low threshold for a suspicious price to 8.99 or below.