Recurly Webhook Not Received or Missed

Share
Workaround available Web (Recurly Admin Console), API Updated November 13, 2026Based on 3 user reportsHow we research

Quick answer

Recurly keeps webhook logs only for a limited time. If a subscription shows active in Recurly, provision manually and make your handler reconcile through the API.

Most likely fix: Check the subscription in Recurly

How to fix it

Try these in order — the most common fix is first.

  1. 1. Check the subscription in Recurly

    1. Confirm subscription status and that the charge succeeded
    2. If active, run your provisioning step manually
    Did this fix it?
  2. 2. Check your endpoint

    1. Public HTTPS with valid certificate
    2. Return 2xx quickly and process asynchronously
    3. Verify the notification types are enabled in Integrations, Webhooks
    Did this fix it?
  3. 3. Do not rely on webhooks alone

    1. Poll or fetch state through the API for critical updates
    Did this fix it?

Symptoms

Your system never provisioned a customer even though payment succeeded.

Why it happens

  • Endpoint unreachable or returned non-2xx
  • Event type not enabled
  • Logs expired, event not replayable

This guide also covers

  • recurly webhook not working
  • recurly missed webhook
  • recurly notifications not received

Still not working?

If Recurly keeps failing, you're not alone. See every Recurly problem users report or the alternatives people switch to.

Have an app idea? Our small team builds any software: web and mobile apps, games, desktop, AI tools. Price agreed together.

Talk to us
Fixed it? Share this guide

Other Recurly errors

All 10 Recurly errors and fixes →