#joshsorenson
1 messages · Page 1 of 1 (latest)
Hi 👋 can you copy/paste the ID of that Subscription here?
@carmine rover sub_1OYGuiBI169bXh55aoW6fBtP
They cancelled the sub at 12:50 and then this ran at 3:27 both on 1/25 and it made the cancellation voided.
Thank you, taking a look.
Can you share the ID of the request where the Subscription had been set to cancel on Jan 25? I'm not readily spotting any requests that would have done that.
@carmine rover evt_1OcYwIBI169bXh55iOUAu1SG
Ah, I see, it was a customer portal update. Hm, that does look odd. Are you able to reproduce that behavior in the test mode version of your flow?
I haven't tried yet
Can you give that a try and let me know how it goes?
Yep confirmed, it happens in test mode too
even when i cancel it from the admin panel
Thank you! We'll need to take a closer look into that.
here is the id for my test mode sub if you need it sub_1Of1zoBI169bXh55Cr1RPzzG
if it's helpful at all updating the metadata on the web admin panel does not reset the subscription to active
Just want to make sure I understand the replication steps correclty.
- Create a Subscription and get it to an active state
- Take any action to schedule it to cancel at the end of the period (customer portal or update through the Stripe dashboard seem to have been tried so far)
- Update the
metadataon the Subscription - Check whether the Subscription is still scheduled to be canceled as expected
Ah, found it
That's expected behavior for the API version you're using. We changed that in 2018-02-28
https://stripe.com/docs/upgrades#2018-02-28
Ah weird, make.com must be using the really old version.
Any ideas on how to change my connection version?
I would recommend checking what your default API version is here:
https://dashboard.stripe.com/developers
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
It sounds like you may be using a third-party integration, and if so you may want to check with the group that provides that integration to see if there are any concerns using it with a newer API version.
Yup, so you're account's default is currently set to 2017-06-05 and that will be used for your requests unless explicity overridden.
Should i be worried about anything breaking in the upgrade? We are using fairly standard fields and not doing anything crazy