Original Summary

Im a solo dev selling a flight & hotel data API, and a week or so ago I found out a paying customer can sit broken for two weeks without a single thing on my side noticing it. He subscribed on the 3rd, 10$ a month, and spent that first evening hammering it, about a hundred calls, nearly all of them fine. Then nothing for five days. When he finally came back every call he made was a 422, rejected in front of my handler before my code ran a search, and he hasnt been back since. A validation rejection logs nothing on my side (no error rate moves, nothing lands in CloudWatch), because the reject happens before the handler runs. So the marketplace dashboard still shows him as an active subscriber, and the last-active date sitting on his row is a call that never reached my code. That scared me way more than the 422 did. He isnt alone either, another failed every call he made that week and then went quiet for good, and I only found either of them by walking every payer's call history by hand. So the validator now logs the field names it rejected (never the values), and my daily read counts a failure streak instead of an error percentage. The reason is that one payer sat at 7.5% while 100% of his calls had been failing for two hours straight, and a percentage was never going to catch that. It caught a new one yesterday who spent his whole first day sending the same wrong field name, 44 calls, all rejected. I still havent written to the first guy, because my own rule says one message per user and he already had his welcome note. Im still a bit sick about the two weeks. Anyways - how do you catch a customer whose calls never reach your code? Would love to hear what you check :)   submitted by   /u/OtherwiseWeekend2222 [link]   [comments]

  • 情报分类：商业与市场研究
  • 分类依据：内容涉及商业、投资或市场动态
  • 信息来源：Reddit · SaaS
  • 发布时间：2026/9/18 20:03:07