Stay in sync
Webhook Doctor & reliability
How MRRdue keeps your dashboard current between manual syncs, and how Webhook Doctor catches the silent failures nothing else does.
Keeping data current
Use Sync now after connecting. In production, configure your provider's webhooks (Stripe or Dodo Payments) and schedule the protected webhook-event, sync-job, raw-event-retention, reconciliation, re-score, and daily-summary endpoints with CRON_SECRET.
Webhook Doctor
Because MRRdue receives your provider's webhooks directly, it also watches them for you. Webhook Doctor flags a signing secret that broke after a redeploy, an endpoint returning errors, and (the one nothing else catches) events that were received but never processed into your data, a silent failure invisible in your provider's own dashboard. See live status and incident history under Webhooks in the dashboard; alerts go to email and Slack on the paid plan. It reuses your existing read-only key, so there is nothing new to connect. For Stripe, granting that key read access to Events additionally turns on a delivery cross-check against Stripe's own event log; that specific cross-check is Stripe-only in v1 — Dodo Payments connections still get every other Webhook Doctor detection.