#harshittyagi_webhooks

1 messages ¡ Page 1 of 1 (latest)

worn bronzeBOT
#

👋 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/1240048710155632670

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

steel scroll
#

Hi there!

#

Not exactly. Can you share more details as to why you want to stop retries? Are you hoping to stop retries for all events sent to a specific webhook or stop retries for a specific event?

glacial berry
#

I am hoping to stop retries for all events sent to a specific webhook.
Our use case is -> We are listening for account.updated event on stripe connect accounts. When connect account onboarding is complete and it is enabled for charges, we need to update a boolean flag in our application database. This is working fine in positive scenario. But, just a edge case scenario .. where let's say that connect account record does not exist in database so there won't be any row to update the boolean column value. We are returning a error code (400) in this case ... and we don't want the stripe to resend these events.

steel scroll
#

Thanks for the details

#

So no, it's not possible to stop retries of a specific event to handle this scenario. Instead, your endpoint should respond to Stripe with a 200 and you should handle the adding of the account record in your database separately (vs. returning an error if the account ID doesn't exist in your database)

glacial berry
#

Okay. Can we stop retries for all events (and not just for a specific event) sent to a specific webhook?

steel scroll
#

There are a couple of options:

  • You can disable a webhook the Dashboard then re-enable later. If a retry attempt happens while the webhook is paused, the retry is skipped. However, if you re-enable the webhook while there are remaining retries for a particular event, we'll still retry.
  • You can delete a webhook endpoint from the Dashboard or API altogether and re-create it. Any pending/to-be-retried event will be deleted and any event created while the webhook was deleted will not be delivered
glacial berry
#

okay. I don't think we want to pause or recreate the webhook.
Anyway, thank you so much for the confirmation.
Have a good rest of your day!

steel scroll
#

You too!

glacial berry
#

If you are still around, one more small thing I want to ask .. do we know the number of retries stripe will do in test and live mode?

#

and at what interval?

steel scroll