#tomfree
1 messages · Page 1 of 1 (latest)
Hello 👋
There's no way to do that. The only option here would be to respond to them with a 200.
can i force a resend try?
It might be possible via the dashboard if the events aren't too old
ok and one can also not delete old test data via api right? so after tests cass with webhooks you basically either have to fake accepting them - which is kind of hard , since you dont know when stripe will retry sending them or manzually delete all test data via dashboard?
is that really the options?
As far as I can remember, you could also delete and re-add a webhook endpoint which might get rid of pending events
vague memory though, not sure if that's 100% accurate
i tried that already - still get old events
Ah I see.
What if you delete the old endpoint and add a different one (changing the path)
could try that. but since stripe wants a real endpoint and not just a local one this would require a new deployment with a new path which on a non-dev environemnt is kind of hard
or is there a way to test not delivered events with a local test instance via strupe-cli?
Ah since you're in test mode, you might be able to use Stripe CLI to resend test events
https://stripe.com/docs/cli/events/resend
ok. that may do
question there. For that to work i need to change the port to which cli forwards. i tried that and restarted and got the same webhook signing secret at before for another port but every incoming event fails validation due to invalid signing. before with the other port all worked nicely. How can I force generation of a new webhook signing secret?