#ironbeard_api

1 messages · Page 1 of 1 (latest)

vagrant badgerBOT
#

👋 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/1471904098411610304

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

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.

mild pelican
#

Hello, I believe that is expected with one-time coupons. The coupon is applied to the subscription's first invoice and that completely uses it up so we don't store the coupon on the subscription
I do see the discount on the invoice that that request created, so that lines up with what I know in_1T0OicE3d1saT86kHWNsxsx0

chilly summit
#

oh, interesting

#

Okay, that's good to know. I appreciate it! 🙂

btw, I've been trying to track down the status of a possible bug I noticed about a year ago that you helped me with: https://discord.com/channels/841573134531821608/1324817116561670194

Basically, it appeared that promotion_code.updated webhook was not fired (with active=False) when expires_at is reached. I think I initially noticed that it also didn't fire when times_redeemed = max_redemptions, but you confirmed that part had been fixed last year.

mild pelican
chilly summit
#

sorry, I don't actually have a reproducible example, I was just following up. I tried doing it with test clocks yesterday, and I don't think it worked, but I wasn't sure if I tested it correctly

vagrant badgerBOT
mild pelican
#

Testing myself I did get an update that shows active going from true to false when this happens for times redeemed at least

  "id": "evt_1T0PPvJmquaq3Lbp8Owz6uYX",
  "object": "event",
  "api_version": "2025-05-28.basil",
  "created": 1771000830,
  "data": {
    "object": {
      "id": "promo_1T0POAJmquaq3LbpAHW7gyK0",
      "object": "promotion_code",
      "active": false,
      "code": "MDQAXGW7",
      "coupon": {
        "id": "hIcNlLV3",
        ...
        "times_redeemed": 5,
        "valid": true
      },
      ...
      "max_redemptions": 5,
      ...
      "times_redeemed": 5
    },
    "previous_attributes": {
      "active": true,
      "times_redeemed": 4
    }
  },
  "...
  "type": "promotion_code.updated"
}```
chilly summit
#

clock_1T05PME3d1saT86kwVtuoJcN was the clock where I tried to apply a promotion code that would expire and then move the clock forward.

mild pelican
#

Oh I misread what you said there. I thought you were saying that times redeemed wasn't working either. Will try to track down that bug report

chilly summit
mild pelican
#

Gotcha, yep confirmed we're still in the same place. I just created a promo code that expired in 60 seconds, it did go inactive but no event was fired.
I pinged on the bug report, but can't promise this time will have better results. Apologies this one hasn't been prioritized.

chilly summit
#

It's okay, I handle it on my side but just didn't know if the code is now stale. Thanks for your time 🙂

#

Is it possible for me to have a reference to the bug report so I can track it in the future? if that's all internal stuff, no worries 🙂

mild pelican
#

Can't give out that detail unfortunately. As long as you mention expires_at and promotion_code.updated we should be able to find it though.

chilly summit
#

Understandable 🙂 Have a great day!