Webhook health degraded
This article explains what to do when MapleGather reports that Stripe webhook delivery has been failing.
What’s happening
Section titled “What’s happening”MapleGather receives notifications from Stripe (called webhooks) to update payment statuses, mark invoices as paid, and fire receipts. When webhook delivery fails repeatedly, payment states in MapleGather may be behind Stripe’s actual state — for example, a payment that succeeded in Stripe may still show as Pending in MapleGather until the next successful delivery.
The warning banner appears on Billing & payments > Payment processor when three or more webhook deliveries have failed in the last 24 hours.
How to fix it
Section titled “How to fix it”- Go to Billing & payments > Payment processor.
- On the Overview tab, look at the Webhook health card.
- Review the per-failure rows. Each row shows the event type (for example,
charge.failed) and an actionable step. - Select Run a diagnostic to open your Stripe Dashboard webhook logs, where you can see the full error details for each failed delivery.
Webhook signing secret changed or invalidated: select Re-verify signing secret on the affected row. This re-syncs the signing secret MapleGather uses to validate incoming Stripe events.
Transient delivery failures: select Retry delivery on the affected event type rows. Stripe re-sends the failed events to MapleGather.
Stripe outage or network issue: no action is needed once Stripe recovers. Stripe automatically retries failed webhook deliveries for up to 72 hours.
If that didn’t work
Section titled “If that didn’t work”- Confirm that your MapleGather webhook endpoint is accessible from the internet (not blocked by a firewall or load balancer).
- If you recently changed your MapleGather domain or URL, select Re-verify connection on the Overview tab to re-register the endpoint with Stripe.
- If failures continue, contact MapleGather support with the event types shown in the failure rows.