#soumit_api
1 messages ยท Page 1 of 1 (latest)
๐ 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/1298294345069232239
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hi there ๐ I see the Subscription in the response is in an incomplete_expired state, rather than canceled. I'm looking to see if the Subscription was already in that state, in which case I think we should have responded with an error here instead, or if this request caused it to move from incomplete to incomplete_expired.
So, the subscription was initially in incomplete state, and I was simulating a situation wherein, the subscription after creation on stripe, failed to be saved on our platform, and we mark this subscription as cancelled, and we pass the cancellation message as "Failed to save data on platform". Though passing this comment in cancellation_details, its neither reflecting in the api response, nor on dashboard
Yup, that aligns with what I'm seeing.
Checking with a teammate because it seems odd to me that we aren't using the value you provided nor are throwing an error.
attached is a postman request response screen for the response of the delete api
Thank you for flagging this! This does seem to be a bug on our end and we're flagging it to the right team to investigate further.
In the interim, you can set those details as metadata on the Subscription, before canceling it, to reference later.
Thanks a lot @stuck finch , that workaround should help