#Sachin_

1 messages · Page 1 of 1 (latest)

quasi sageBOT
undone ingot
#

Can you provide an example?

zealous ginkgo
#

Like i was working on a application . I was listening for stripe webhook. Same code is on server and there is one webhook added for that in stripe. And locally i am using same application and also listening by stripe cli.

#

So issue is that. When my local machine is off . Then that webhook call fails and also on web i forgot to return 200 status on the success.

#

Now old webhooks keep hitting for server beacuse that was not a success call . And retry call for local one with ngrok or local cli listener.

#

So i want to stop old schedule d webhooks.

#

Is there any way ?

undone ingot
#

You have a webhook configured on your Dashboard to send to your local dev environment?

#

Can you share an evt_xxx ID?

zealous ginkgo
#

Yes i configured to send on local

undone ingot
#

Can you share an evt_xxx ID?

zealous ginkgo
#

evt_1M2ubLCPcXP7FuxJXKUHeUBc

#

I want to cancel all the pending webhook calls.

undone ingot
#

Are you using the CLI to listen and forward events (like that one 👆) in development?

zealous ginkgo
undone ingot
#

Then why do you also have webhooks configured that points to ngrok URLs?

#

They're redundant if you're using the CLI, just delete them

zealous ginkgo
#

Before i was not using cli. Also had to share with another developer.

#

Yes today i deleted ngrok url.

#

But also main server webhooks were treated as failed webhook. Because i was not sending satatus 200 acknowledgement to stripe.

undone ingot
#

There's no way to prevent the retries. They'll lapse eventually (normally ~3/4 days after initial delivery attempt)

zealous ginkgo
#

Now i had done my business logic in my app . But that failed requests are coming again and full app logic is being destroyed.

undone ingot
#

Yep! We always recommend testing first with the CLI, and best practices requires you return a 2xx response ~immediately

zealous ginkgo
zealous ginkgo