peljoe_webhooks

[hollow vale]

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

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

[old pine]

hi! have you investigated this on your side and looked into what responses your webhook code is returning and why?

[drowsy rampart]

hi, with no access to stripe logs, I did check our app logs and there are no exception, so I don't really know where to check

As we didn't update our app, I think it comes from an api change though

[old pine]

well you must be returning a non 2xx response or we wouldn't be emailing you?

do you have an example event ID evt_xxx where we told you you responded with non-200? (maybe not if you don't have Dashboard access)

[drowsy rampart]

not without dashboard screen yet

[old pine]

we don't really change the API in breaking ways no, but it's hard to say without some details from you as to what's actually happening in your webhook handler and how/why it returns an error.

[drowsy rampart]

the issue is because we are now receiving checkout.session.expired, which is new

since apr 20

[old pine]

https://docs.stripe.com/upgrades#what-changes-does-stripe-consider-to-be-backwards-compatible

Stripe considers the following changes to be backwards-compatible:
Adding new event types.
Make sure that your webhook listener gracefully handles unfamiliar event types.

[drowsy rampart]

thank you, issue identified

have a nice rest of your day

[old pine]

you too!