Allow us to retry pending...

[Eric Brown]

For some reason Stripe wasn't able to connect to our web server and call the web hook.  We host our web hook in Windows Azure so it should have been available but according to the log there was an error connecting to it.  It would be a really nice feature to add a button to this page that allowed us to request a retry rather than waiting however long to test to make sure everything works as expected.

Any chance you guys can add a retry button?  If you have a concern about it being hit too much, perhaps you could limit the number of times we can retry in a given time period or something?

Thanks!
Eric

[Andrew Metcalf]

Hi Eric,

Thanks for the feedback.  This isn't on our immediate roadmap but it's good input for our future thinking.

Sorry I can't be of more help for now!

Best,

Andrew

[Eric Brown]

No worries, I did notice there is a retry button when you switch to test, just figured it would be nice to have in live as well.

Thanks!
Eric

[jay...@nsfwcorp.com]

For what it's worth, this would have been useful to me a couple of times; having to wait for the automatic retry is painful, and correctly setting up a similar situation via the test keys is dicey at best.

[Dennis Vasquez]

Hi Andrew,

How long does it take for Stripe to 'Retry' a pending webhook?

My host was down because of maintenance, and of course, orders came in at that precise moment LOL

They can't get access to my product until Stripe retries the webhook.

Any update on manually retrying?

Much thanks,
Dennis

[Remi J.]

Hey Dennis,

Whenever we attempt to deliver an event to your webhook endpoint we expect a 2xx response code to indicate that you handled it properly on your end. If you respond something else, we assume that you didn't get the event.

At the moment, we try to deliver it again every hour for up to three days before giving up on that event completely. That interval of retrying every hour is not set in stone and could change in the future though. It's possible we'd prefer to quickly retry once or twice and then increase the time between each retry until we give up. For now though, if an event delivery has failed you should see another one an hour later or so.

Cheers,

Remi

--
You received this message because you are subscribed to the Google Groups "Stripe API Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to api-discuss+unsubscribe@lists.stripe.com.
To post to this group, send email to api-d...@lists.stripe.com.
Visit this group at https://groups.google.com/a/lists.stripe.com/group/api-discuss/.

[JP Sugarbroad]

I have had this happen before, and what I did was to generate a synthetic web hook call. Then when stripe delivered the actual call later it was processed as a duplicate.

[Minghua Zhao]

Hi Remi,

I see this is an old topic, but the same thing happened to us, and we missed the failed Webhooks for 3 days.

Is there something I can do to re-trigger those Webhooks?

Best,

To unsubscribe from this group and stop receiving emails from it, send an email to api-discuss...@lists.stripe.com.

[Remi J.]

Hey,

The best option would be to handle this on your end. Your code would fetch the event payload directly from the API [1] and feed it to your webhook handler. Another solution would be to use something like this tool [2] to re-send all those events to your endpoint.

Hope this helps!

Remi

[1] https://stripe.com/docs/api#retrieve_event

[2] https://github.com/anelder-stripe/retry-events

To unsubscribe from this group and stop receiving emails from it, send an email to api-discuss+unsubscribe@lists.stripe.com.