#binodkafle_webhooks
1 messages ¡ Page 1 of 1 (latest)
đ 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/1332276830505537548
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Yeah this is just how it works if they're all working in the same account/test env. Ideall you'd probably want to leverage Sandboxes and give each dev their own: https://docs.stripe.com/sandboxes
But that's a preview right now
The other way is to leverage metdata on the objects/events and then add logic to the webhook code to check before processing the event
Is there a way to flush all pending webhook events from the Stripe dashboard? Currently, we have to manually resend the webhooks and ensure a 200 OK response is returned for each event. Is there a more efficient way to handle this?
You could use the CLI to trigger resends, but you can't clear the pending ones no. They're subject to automatic retries
Thank you for your help.