Menu

Webhooks That Stopped Arriving: Gap Detection & Reconciliation
📰

Webhooks That Stopped Arriving: Gap Detection & Reconciliation

DEV Community: laravel·Muhammad Ali Mughal·7 days ago
#UTM2SfvR
#devtolaravel#devto#dev#provider#event
Reading 0:00
15s threshold

A customer emails: "I cancelled my plan three weeks ago, why was I charged again?" You check the billing provider. The cancellation is there. You check your database. The subscription is still active. Your webhook handler has no errors, because for three weeks it received nothing to fail on. The provider disabled your endpoint after a run of failed deliveries, sent one email to an address nobody reads, and moved on.

I wrote this with help from AI tools and checked every migration, query and command myself. I am a Principal Software Engineer in Karachi with 9+ years across PHP/Laravel, Vue, Node and .NET microservices, and at Loop Origin we build and maintain SaaS backends that depend on payment, shipping and identity webhooks. This is Part 2 of the series Silent Failures in Production SaaS. Part 1 covered cron jobs that never ran ; webhooks are the same class of problem pointed the other way. Your code is fine.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.