#deadshot_api

1 messages ¡ Page 1 of 1 (latest)

solar rampartBOT
odd iceBOT
#

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.

solar rampartBOT
#

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

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

gloomy owl
#

hi there!

vestal sun
#

Hi

#

I want remove the remaining time proration on the given invoice ID. I don't get how that happens because the new phase is starting exactly at the same time

gloomy owl
#

it's a bit tricky to understand your issue since your schedule has many phases, and you updated your schedule. is there a way for you to simplify things to isolate the issue?

vestal sun
#

Sorry, it's simplified enough and close to my current workflow

#

I create a subscription schedule and then I add a new phase. The issue occurs in the invoice for newly added phase.

gloomy owl
#

is the only difference when you update the schedule is the addition of the last phase?

vestal sun
#

My last phase is a 2 days phase with 100% off discount applied and after adding a new phase, the remaining 5 days from the last phase is prorated into the next invoice

gloomy owl
#

but you set proration_behavior: "create_prorations" in phase[3]?

vestal sun
#

Thats because I need proration in phase[3]

#

But seems like the proration is created for phase[2] which is none?

gloomy owl
#

I'm sorry, there are just too many updates to your subscription schedule, and it's too difficult for me to follow what's going on.
please create a schedule with just one phase, then update it once to two phases, while reproducing your issue. then I'll be able to investigate.

image.png