srbartlett_webhooks

[spark sky]

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1237614491378913341

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[mortal hornet]

The webhooks will not be queued, they will retry I believe 3 times within an hour, but in your use case it would be ideal to have a queue service to receive them and process them when your application is back online.

[grizzled root]

thanks! I guess it is better to not disable the webhook and either a) queue in the app, or b) return a non 200 status code, eg 400 so that Stripe will retry (but only for 1 hour) ?

[kindred drift]

No, if you disable the webhook the retries will be paused

While a webhook endpoint is disabled event delivery and retries that would normally be attempted will cease and will not be sent again, even if the webhook is re-enabled. However, once the webhook endpoint is re-enabled event delivery will resume, including future retry attempts. Consider this example timeline showing how disabling a webhook endpoint won't prevent all future retries:

1. Event delivery attempt failed, so retries are scheduled
2. Webhook endpoint disabled
3. Time to retry, but the webhook endpoint is disabled, so retry is skipped
4. Webhook endpoint enabled
5. Time to retry again, webhook is enabled, so retry is attempted