#nukesforbreakfast-failure-emails
1 messages ยท Page 1 of 1 (latest)
Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- nukesforbreakfast, 6 days ago, 18 messages
HI ๐
We don't have another way to notify users immediately of failing webhooks. Webhooks are the tools we use for rapid notification and I'm sure you could see how that could snowball if we sent a webhook event every time a webhook event failed to deliver.
Ultimately this is up to your network to flag
sorry, I'm talking about an email notification to the support email on file or however it works today.
right now, if webhooks fail for some time, Stripe eventually sends an email notifying the devs that "yo, your webhooks are failing more often than not."
I'm looking for a way to tune that notification email to be more aggressive.
so at the first signs of trouble, stripe lets us know.
No, currently we only send emails if the webhook delivery failure is recurring
And we won't be changing that.
so there's no way to opt in to a more aggressive email notification schedule?
Correct
damn, that sucks. Alright well thanks for letting me know.
Unfortunately the responsibility to log these failures is with the network gateway. Is that something you can configure via logging and actions?
One thing you could do to get more immediate notification is to add a check in your webhook handler for the pending_webhook property. This will notify you of any webhook events that have not been successfully delivered. It depends on you receiving a webhook after the delivery failure but depending on the frequency of webhook events you receive this might be pretty fast.
https://stripe.com/docs/api/events/object#event_object-pending_webhooks
I could tune it, but the 400s are hard to properly account for given that some bad actor could be trying to send improperly signed webhooks, resulting in 400s.
Yes, in that case using the pending_webhooks property, only after you have verified the Event, might be the best option
okay, that sounds like the right thing for now. It would be nice to be able to further tune the developer oriented email notifications via the dashboard. This in my mind would work similarly to tuning how often Invoice reminder emails are sent.
That makes sense and I can raise that as a feature request internally. I doubt we would have a cadence higher than per day though. Otherwise we might crash some email servers ๐
I have filed the developer email configuration feature request you asked for. If you would like to follow along you can write in to Support https://support.stripe.com/contact and mention you were talking with me (Snufkin) and I can ensure you are updated if that feature is ever implemented