#xaositect_best-practices

1 messages ¡ Page 1 of 1 (latest)

undone rainBOT
#

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

📝 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.

pseudo ermine
#

Hi there

magic juniper
#

Hello

pseudo ermine
#

I'm aware there may not be a better way to deal with migrating from forever coupons, but seemed like it was worth asking y'all.

magic juniper
#

Yeah thanks for asking. There isn't a perfect workaround right now -- we are working on some new Coupon shapes that will be released in the future, though I don't expect those to be perfect replacements either but would result in an improved state. For now, you can still use duration: repeating with a long period of time like you have stated. There is active work being done on a suitable replacement for duration: repeating Coupons that will be available before those are deprecated in a future version.

#

Actually I'd assume that replacement would suit your use-case for duration: forever as well.

#

My understanding is that it will be a "service period" type of Coupon

#

So it could apply to the entire duration of a Subscription for instance.

#

But it is still under development so I can't promise the final shape of that.

pseudo ermine
#

That would be helpful, right now we're doing a lot of cloak and dagger to associated previously used coupons to customers in a way that doesn't allow them to reuse them.

Out of curiosity, was the movement away from forever a product or technical decision? I can't imagine we're the only group in this situation.

magic juniper
#

I'm not 100% sure... I believe it was a technical decision.

#

We have certainly heard feedback (and have been passing it along to the Eng team) that this has been disruptive.

#

We are pushing to ensure there are proper replacements in place in the future before a deprecation of this nature happens again so that we don't get in this spot again.

pseudo ermine
#

I appreciate that. Thanks for the advice and news about forthcoming updates.