#dominikganic_unexpected

1 messages · Page 1 of 1 (latest)

crude axleBOT
#

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

📝 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.

summer vessel
#

Hi again. Sorry!

#

One quick question. Why does it show "Aktualisierung geplant" which means "Update Scheduled"?

#

Reproduction Steps:

  1. Customer has created a subscription (10.02.2025)
  2. Customer wants to downgrade to a lower subscription model, which is okay
  3. We create a subscription schedule with start_date 10.03.2025 (once this month passes)
  4. The schedule takes action and has been converted to a normal subscription (no schedule anymore)
  5. It display "Updates Scheduled"?
dapper dirge
#

Hello! Can you give me the ID of that Subscription so I can take a look?

summer vessel
#

sub_1Qr2TvLZihhBkt1c2iPrw3xT

dapper dirge
#

That's normal. As you mentioned, you have a Subscription Schedule associated with that Subscription configured to update the Subscription in the future, hence the "Updates Scheduled" badge in the Dashboard.

summer vessel
#

But, it's no schedule anymore in this case, the time has already passed 5 days overdue the schedule took action

dapper dirge
#

That's not what I'm seeing. I'm seeing that there is still a scheduled update in the future.

summer vessel
#

For example:

User created a subscription today (10.02.2025)
Now he downgrades, we create a schedule for 10.03.2025
Now it's the 15.03.2025 and the schedule has taken action, the lower subscription is active, but it still displays the badge.

dapper dirge
#

Right, that update is in the past, but there's another update scheduled for 2027.

summer vessel
#

o.O

#

Really

dapper dirge
#

Yes.

#

Note the start_date provided there.

summer vessel
#

Ah, fyi, I'm using test-clocks and I'm currently in 04.12.2027

#

That's my behavior right now.

When a customer wants to downgrade, I

  1. Set the currrently active subscription to "cancel_at_period_end" to true
  2. Create a schedule with start_date -> current subscription end date
  3. Await the process..
image.png
dapper dirge
#

Right... again, please have a close look at that start_date timestamp.

summer vessel
#

That's correct yes, it took action on 30.11.2027?

#

As my simulated time is currently 04.12.2027

dapper dirge
#

Right. November comes after April, so it hasn't happened yet.

#

Wait...

summer vessel
#

Ah sorry

#

I'm in germany xD

dapper dirge
#

Are you saying your test clock is currently set to April or December?

summer vessel
#

It's not april

#

It's december yes

dapper dirge
#

Let's switch to using YYYY-MM-DD dates to eliminate any confusion. 🙂

summer vessel
#

yes 🙂

#

start_date is 2027-11-30

#

test clock time is 2027-12-04

#

The schedule took action on the correct day and everything went fine. My active subscription got canceled as expected and the new one is active now.

#

But the badge is still displaying, that's confusing.

dapper dirge
#

Okay, so your test clock is currently set to 2027-12-04 and you're seeing the "Updates Scheduled" badge for sub_1Qr2TvLZihhBkt1c2iPrw3xT in the Dashboard. Let me have another look...

summer vessel
#

Yes sir! 🙂

#

FYI: When I simulate the time forward to the next month the badge disappears

#

(Without any significant / visible changes)

dapper dirge
#

Oh, I see. The Subscription Schedule's phase is still active. The phase runs from 2027-11-30 to 2027-12-30, and your test clock is in the middle of that, so it's showing you that updates are scheduled. The Subscription Schedule is configured to release the Subscription from the Schedule after the current phase ends, so no change actually happens, but the system doesn't assume that will be the case (the Subscription Schedule could be modified to make an actual change, for example).

summer vessel
#

Ahhh okay. So in my phases object I have items, metadata etc., should I set there as well a start_date or something similar to prevent this behavior and make it the correct way?

#

end_date for phases should be start_date of the schedule itself maybe?

dapper dirge
#

I'm not sure if it will like that, but you could give it a try, yeah.

#

I think you're doing the right thing and it's doing what you want, it's just the Dashboard isn't displaying it exactly the way you expect.

summer vessel
#

Okay, let me give it a try for a sec 🙂

crude axleBOT
summer vessel
#

"Each phase must be at minimum 1 second long. Phase 0 has the same start_date and end_date of 1835450880."

#

Okay I've just added + 1 and now it works just exactly how I've expected everything to work 🙂

#

Thank you again Rubeus, you're awesome! Have a nice day. Think that's enough code for me today. (: