#rob_unexpected
strong zenithBOT
👋 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/1460609640541851690
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
jaunty ember
this was in the response / go package
Docs of the API version called
Relevant event evt_1Sp55pGcuLQxtiNKIoODJY0N
rigid rain
👋 happy to help
taking a look at the event
cancelAtPeriodEnd hasn't been set
so even if the CancelAt is the periodEnd, that doesn't mean that we automatically re-evaluate the CancelAtPeriodEnd to true
jaunty ember
cancelAtPeriodEnd hasn't been set
Do we need to set this on our side you mean?
so even if the CancelAt is the periodEnd, that doesn't mean that we automatically re-evaluate the CancelAtPeriodEnd to true
I'm sorry but I think I'm not knowledgable enough to understand what you mean by this
Can you maybe rephrase it?
rigid rain
I mean that, if you set it to true, you don't have to calculate the CancelAt
we will do that for you
but the other way doesn't happen
jaunty ember
But before (older version of API) when creating a billing portal cancel session, the CancelAtPeriodEnd would return true, now it returns false? Do we have to change the way we create a billing session?
rigid rain
would you mind sharing an example where this happens?
jaunty ember
params := &stripe.BillingPortalSessionCreateParams{
Customer: &team.StripeCustomerID,
FlowData: &stripe.BillingPortalSessionCreateFlowDataParams{
Type: stripe.String(string(stripe.BillingPortalSessionFlowTypeSubscriptionCancel)),
SubscriptionCancel: &stripe.BillingPortalSessionCreateFlowDataSubscriptionCancelParams{
Subscription: stripe.String(team.StripeSubscriptionID),
},
},
ReturnURL: stripe.String(returnURL + "?action=subscription_cancel&success=true"),
}
When we create a billing portal URL like above, in the old version when the user cancelled the sub in the billing portal, a webhook would be called with a subscription update, with CancelAtPeriodEnd set to true. Now, this same webhook returns false for that field
rigid rain
I meant request IDs or subscription IDs
jaunty ember
for test
jaunty ember
and prod is the same
rigid rain
we need to escalate this
would you mind opening a ticket with https://support.stripe.com/?contact=true
jaunty ember
Will do, thanks!
rigid rain
let them know that you've already spoken to us and that we sent you there and that we verified it's a bug
jaunty ember
How do I actually report a ticket? 😅 The link you sent only has the AI assistant and some help docs? If I click Contact support in the sidebar it opens the AI assisant, which I gave the bug report but it told me to Report it through official channels - File a bug report through Stripe's official support channels or GitHub issues for the Go SDK
strong zenithBOT
jaunty ember
It did work, kinda. I sent an email via https://support.stripe.com/contact/email?topic=api_integration which allows to send an email, which is fine. I can defer the update and otherwise work around it.
But does raise the question from my PO, how can we now be sure that we don't have more breaking changes when updating the API? I find it hard to find relevant docs that state the behavior of CancelAtPeriodEnd got depcrecated/changed.
waxen narwhal