#birdy247
weary dustBOT
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.
- birdy247, 2 days ago, 19 messages
dreamy prawn
👋
fiery rampart
Hi
Maybe a silly question(s)
- Can we change the frequency of a stripe webhook to be retried?
- Lets say stripe emits a webhook, and our server is underload. How long will the webhook wait until it times out?
dreamy prawn
1/ No
2/ We don't guarantee a specific amount of time, but it is quite quick (generally a few seconds). You would want to either wait for the retry or you could list Events (https://stripe.com/docs/api/events/list) and check if there are pending ones and you could go ahead and ingest the data via the list API if necessary to have it immediately.
fiery rampart
We saw a number of our webhooks showing a 500 response from us
This happened as our server was under load
Could it be that we didnt respond quick enough?
fiery rampart
Would that lead to a 500 on the webhook?
dreamy prawn
Not sure what you mean by that?
If you see a 500 response for the Event that means your server never responded, or responded with a 500 explicitly.
Usually there should be a timeout indicated I believe if it was due to a timeout
fiery rampart
Ok, so no response could be because our server was running slow?
dreamy prawn
Yep
dreamy prawn
We generally recommend that you respond immediately to Webhooks and then cache the data and handle it async on your end if you are overloaded.
We don't guarantee any sort of timing, that is what I mentioned above. But yes, we expect the response to be made quite quickly.
dreamy prawn
Yep
fiery rampart
I guess we should also limit the wehbooks sent
dreamy prawn
It is recommended you only listen to Events that your integration uses, yes.
fiery rampart
Another q
Sometimes we see connected accounts who use their stripe a/c for other things
This leads to us reciveing webhooks for payments we never initiated
This then shows as a failed webhook in Stripe
Would we be better to just return a happy response to stop you retrying those?
dreamy prawn
Yep that would be better.
If you receive a Webhook successfully then you should always return a 200.
What you do with the data afterwards is up to you
So in this case you would just ignore it
fiery rampart
👍