#chris-subscription-bug

1 messages · Page 1 of 1 (latest)

knotty hearthBOT
#

Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

stone elm
#

Hi 👋 I'm not sure offhand, let me see if I can find anything about that.

#

I'm not quickly finding anything about that either way. Do you have examples from your testing that you can share showing that limitation being ignored that I can take a closer look at?

modest mango
#

Here's a test that I did through the test terminal.
The promo code has first time only restriction on it
The customer has many purchases
I would expect that the response would either be an error regarding the promo code or that the coupon wouldn't be applied

stripe invoices upcoming --customer="cus_PVWNYFRD4M3MYr" -d "invoice_items[0][price]=price_1OiPkwJXnoT78czAKbnGBszS" -d "invoice_items[0][discounts][0][promotion_code]=promo_1OiQSmJXnoT78czALbdE36bM"

#

Sorry, I'm new to Discord and I'm not sure if the results made it through. I see that as I hit enter, it did load a preview

📎 message.txt
stone elm
#

Yup, it came through, taking a look.

knotty hearthBOT
stone elm
#

I see what you're saying, it definitely looks like we ignored the restrictions there.

#

Looking again for any context about whether that is expected.

modest mango
#

OK, I was fighting with that and trying to figure out what the heck I was doing wrong to get those results back.

stone elm
#

Apologies for the delay, I'm still trying to get that clarity for you. If I'm not able to get it for you soon though, it might be better for you to reach out to our Support team with this inquiry, as support tickets are better suited for longer discussions like this may need.

modest mango
#

Thanks. Since we're both reading the docs looking at the results and thinking this isn't working correctly, if it's not supposed to work that way could you create a bug report?

stone elm
#

Yup, I can certainly do that, but you won't hear the outcome of it here.

modest mango
#

Fair enough. I had to pivot the way I'm handling a couple of things due to this but at this point I just wanted to make sure that I wasn't doing something wrong and find out if it was an intended behaviour or a bug and that it would get a ticket in if it's a bug.
And have that backup to tell my boss why I haven't completed this part of the project 🙂

stone elm
#

👍 totally get it, I'm also working on testing replication in my account, I'll let you know if I find that I'm able to see that behave the way you and I think it should.

modest mango
#

Excellent. I appreciate your effort.

stone elm
#

Thank you so much for your patience as I dug into this and for taking the time to raise this to us! I am seeing the same behavior in my account, and our teams do currently see this as unexpected behavior and are taking a closer look at it.

knotty hearthBOT