#oleg-codaio_api
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/1279154927897415883
đ 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.
- oleg-codaio_api, 19 minutes ago, 45 messages
Ah, looks like the bug just went out to production / live mode
req_GQ7hKRGkXqRhWC is failing
cc @fast harness
Hi, how can I help here? Can you add more context?
Just following up on the other thread: #1279126193030824017 message
Are you still investigating this issue? Looks like the regression went out to production. Is there an ETA for the fix yet? This is causing our customers not to be able to change plans
Can you summary the ask here please? I am catching up and helping other on the server too so it would be helpful if you could provide a summary here.
Sure - there's a bug where changing a subscription from monthly to annual and passing in pending_invoice_item_interval now results in the following unexpected error:
When set, the pending_invoice_item_interval must be more frequent than the natural subscription interval.
Initially we were only able to reproduce this in test mode, but looks like this now reproduces in live mode.
@fast harness acknowledged this is a known issue internally and said it's under investigation
Can you provide an update on the fix?
Looking, I'm here so you do not need to ping the previous person who was helping. I just need to understand your ask fully before I can help you properly.
I see, we are internally investigating this issue still. I will provide an update as soon as I can. In the meantime, I will leave this thread open so I can ping you with an update
Alright, thanks.