#jasuno_api

1 messages ¡ Page 1 of 1 (latest)

pastel surgeBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1259863235700588546

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

gritty sailBOT
glacial fractal
#

Hello, thank you for the request ID. Looking in to this and will get back to you

neat widget
#

Thanks

glacial fractal
#

Ah it looks like that change was made, but when your subscription schedule advanced, it overwrote those settings

#

If you update a subscription when it has a schedule, that will only update the current phase, phases going forward will not be effected. So to do this update, you will want to update the subscription schedule, and will want to modify that price and transfer data on each phase

neat widget
#

Thats interesting, does that only happen some times because i tested it a few different times and it was working, let me look for the request ID

#

sub_1PaH0gAq6ReFUKV8L6MjDzRK this subscription seem let it changed, it also had a schedule and different phases, do you know what the difference was?

glacial fractal
#

Good question, looking in to that ID and will get back to you

glacial fractal
#

Apologies, the server was extremely busy and I just got to start looking at this. What update specifically was respected here after the test clock advanced?

#

From what I can see, the metadata and payment method types that were set by your API calls were the settings that were already on the subscription.

neat widget
#

Would that affect the update?

glacial fractal
#

That would mean that the update is a no op. If the metadata or payment_method_types did differ from the existing subscription, that would have only effected the first phase again as far as I know

#

If you have another example or can quickly consistently produce the behavior where it seems to affect all phases, I am happy to take a look. But as far as I can see on that subscription, the update API calls didn't end up updating anything on the subscription or schedule

neat widget
#

Ok let me check