#diegot_webhooks

1 messages ¡ Page 1 of 1 (latest)

clever beaconBOT
#

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

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

little brook
#

I'm listening for events using this command with my local url stripe listen --events customer.subscription.deleteld --forward-to

brazen root
#

There isn't a way to simulate that for an actual subscription without actually cancelling it. Can you tell me more about what you are testing and why you are trying to get this event without actually cancelling?

little brook
#

the flow I'm defining is already tested from our side, We are creating a new checkout session, and then we have a mechanism to process when the subscription from that checkouts is cancelled to trigger an internal process. If I manually cancel the subscription and I'm listening for events using the cli listen command, am I going to receive the event?

#

I tried to override the subscription id like this
stripe trigger customer.subscription.deleted
--override subscription:id=sub_xxxxxx

But it seems the customer.subscription.deleted flow is simulating the whole flow, new customer, new products, new prices, new subscription

brazen root
#

Yep that is expected there. And you should receive the event unless you told the CLI to only listen for certain events and the list didn't include that event. What might make more sense for you to do here is actually cancel the subscription, get the evt_123 ID for that deleted event, and run stripe resend evt_123 to resend it.

#

Is your listen command receiving any events? Or is the deleted event the only one that doesn't seem to show up for you?

little brook
#

I can see the listen command is receiving events (included the delete ones)

#

I'm going to try that approach resending the evt_id, thanks!!