#cm5061_api
thorn birchBOT
👋 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/1294299923965018214
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
storm folio
Looking into this
thorn birchBOT
supple plaza
Hi there 👋 jumping in as my teammate needs to step away soon. We're reaching out to the right team about this on our end. Based on what we're seeing that error doesn't seem to make sense for your scenario.
vernal folio
Thank you @supple plaza and @storm folio !
supple plaza
Still discussing this with our teams, but it looks like your suspicion is right here, that this is erroring because the Subscription's first payment isn't completed yet. It's not clear yet whether that was the intended behavior of this check.
supple plaza
We've rolled back this change while we take a closer look at the logic we have there. Thanks for taking the time to flag this!
vernal folio
Np, thank you! I think conceptually it kind of makes sense that Subscription updates could be blocked before that initial payment settles, although it was a little surprising because it's a deviation from past behavior wrt. the API
It's probably the most belt & suspenders "correct" approach.
OTOH, although it seems correct, idk what the actual harm would be in allowing the update? If that first payment doesn't settle the Subscription just expires, it's not like we'll be triggering additional invoices from it, etc.
Either way, appreciate you looking into it!