#worming_best-practices
sand hamletBOT
đ 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/1402026933587415162
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
dense grove
Hello, do you have the ID of a subscription that you have seen this behavior on? I would also expect it to behave the way you described because that is how it has worked on my test subscriptions before
remote burrow
sub_1RsUmpLN0iJa18ZenYCIxPze
the subscription is on the test mode
yes, we were doing that before and it was working, im testing a new flow with a similar code and im getting a different behaviour, so i could be something that we are doing wrong
dense grove
The update for that subscription specifically sets quantity to 0 rather than setting deleted to true
https://dashboard.stripe.com/test/logs/req_IaQ6RsLjuu3aQB
Can you show me your code for making that update? I don't think our SDK would swap out those parameters
remote burrow
.Net
var subscriptionItemOptions = new List<SubscriptionItemOptions>();
..among other things...
subscriptionItemOptions.Add(new SubscriptionItemOptions
{
Id = currentItem.Id,
Plan = currentItem.Plan.Id,
Deleted = true
});
...
if (subscriptionItemOptions.Count > 0)
{
var ep = new Dictionary<string, object>();
ep.Add("proration_behavior", "none");
SubscriptionUpdateOptions subscriptionOptions = new SubscriptionUpdateOptions()
{
ExtraParams = ep,
};
subscriptionOptions.Items = subscriptionItemOptions;
stripeSubscription = subscriptionService.Update(stripeSubscription.Id, subscriptionOptions);
}
wait! ...let me check something... it could be a bug in my code... i will let you know
dense grove
Can you try re-running that one more time and printing out the request ID right after? I'm still seeing the proper bebavior in my tests https://docs.stripe.com/api/request_ids
remote burrow
i think it is a bug in my code, give me a minute and i will let you know...
sand hamletBOT