#piyush_best-practices
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/1428095612405940245
đ 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.
- piyush_unexpected, 5 hours ago, 13 messages
- piyush_docs, 1 day ago, 14 messages
- piyush_docs, 2 days ago, 12 messages
- piyush_unexpected, 2 days ago, 38 messages
- piyush_subscription-update-invoice-preview, 5 days ago, 22 messages
- piyush_docs, 6 days ago, 18 messages
Hello, from subscription creation is the expected behavior here. We don't re-adjust the cycle based on when the payment actually happens. You can reset the billing cycle if you want it to re-adjust but keep in mind that that will create some complexities around handling subscription cycles through webhook events and such.
what kind of complexities, that's just increasing the subscription by a day approx. without any extra charge
Sorry I was vague there. I think the main thing to do is make sure your system knows how to recognize when the subscription is cycling because of this initial adjustment vs it cycling as time passes going forward. Like if you have a webhook handler that listens to customer.subscription.updated events it would need to have a check added for this situation. So not incredibly complex but I can see it being easy to miss
yeah, it should only be on first state transfer which is incomplete to active as i see it, right?