#_unexpected

1 messages ¡ Page 1 of 1 (latest)

lucid hazelBOT
#

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

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

fathom marlin
#

Can you share the request id where you see the error?

#

req_xxx

lost turret
#

req_nBvCIk3z9CVseV

#

I see in console ui

dapper adderBOT
opaque sigil
#

Hi @lost turret I'm taking over this thread, give me a sec to catch up

#

Also in req_nBvCIk3z9CVseV, you were trying to update the start_date of phase 0, but phase 0 is already started. Can you try again without setting start_date of phase 0 ?

lost turret
#

Are you saying that the epoch time is the same, but it's considered different? Isn't the start_date a required field?

opaque sigil
#

Yes you are right, the start_date of the first phase is required. Sorry for the confusion

Can you use the same value (i.e., 2024-07-19 07:52:39) as the start_date of phase 0?

lucid hazelBOT
lost turret
#

I used epoch time, it was same value. (1718783500)

#

2024-07-19 07:52:39 value is end date of phase 0

still token
#

That unix timestamp is in June so not 2024-07-19 07:52:39

lost turret
#

i requested
phase 0 start_date 1718783500 (2024-06-19 07:51:40)
phase 0 end_date 1721375500 (2024-07-19 07:51:40)

phase 1 start_date 1721375500 (2024-07-19 07:51:40)

the period of subscription is below image

image.png
#

as far as i know, first index means current phase

#

Sometimes the phase length is 3, and phase 0 points to the past, but the release doesn't work well. Is this normal, or does it only happen in test mode?

still token
#

Test and Live mode would mirror each other so no.

lost turret
#

So, is it possible for there to be a case where the phase length is 3?

#

When is the point at which past phases are automatically released?

still token
#

What does 'phase length is 3' mean?

lost turret
#

Generally, when setting the subscription schedule, the current period goes into phase 0, and the next schedule goes into phase 1. However, in test mode on Stripe, there are cases where the data appears in the order of [past phase, current phase, future phase].

still token
#

I'm having a hard time undertstanding the question here. Can you share examples of what you expect to see and what you're seeing in details?

lost turret
#

Oh, what I just mentioned is separate from the current issue; it was something I was curious about in general.

I have reproduced the current issue, and the subscription ID is sub_1PTcTiIX9E6NiiqiyzxVXfH6. Could you take a look at it?

#

Just now,

1.Created a customer,
2.Created a subscription with quantity 1,
3.Changed the current phase of subscription to quantity 2, next phase quantity 1.
4.Tried to change the next phase from 1 to 2, and the issue occurred.

#
  1. req_qGjUf4KxWaPMjP
  2. req_LHXsEbIEH626mn
  3. req_UY0Wc6oHzMOjhF
  4. req_l4Sh0s4bK675yL
still token
#

I'm attempting to reproduce what you're seeing, thank you for your patience.

#

While I'm still looking into this, can I ask why you're creating the subscription with 2 quantity, then updating it to one, then updating it to 2?

lost turret
#

Currently, our service has a seat feature that is linked with the subscription quantity. If a member leaves, the number of seats should decrease in the next cycle.

still token
lost turret
#

It seems like the logic is setting the next phase. Is there an issue with that?

still token
#

At the moment, just trying to understand what you're attempting to do on my reproduction

lost turret
#

in the past, this process is working well, but recently it is not working.... we have to control phase of schedule for payment.

still token
#

Can you share an example where it worked before?

lost turret
#
  1. create customer
  2. create subscription 1 quantity
  3. update current quantity of phase 0 to 2 if user buy seat. and set next phase quantity to 1
  4. when user invite member into team. update quantity of next pahse(1) to 2,
  5. when member leave from team, and then update quantity of next phase(1) to 1.
still token
#

Can you share the request ids where this worked similar to what you did above?

lost turret
#

I already shared. above.

#

req_qGjUf4KxWaPMjP
req_LHXsEbIEH626mn
req_UY0Wc6oHzMOjhF
req_l4Sh0s4bK675yL

still token
#

you stated that it was working before

#

can you share the request ids where it was working?

#

The ones you shared are the ones that are not working

lost turret
#

in live

  1. req_TckSrzjIoPhPAE upgrade quantity current phase

  2. req_e0q5LGRJj1EIDc set next phase seat

  3. req_5oQlAhqILTJhRF upgrade quantity current phase

  4. req_dxHiJSGw0A0MFc set next phase seat

  5. req_04zoKzBVgO6Gsq downgrade next phase quantity

still token
#

Thank you, looking.

still token
lost turret
#

I don't understand your request

#

I can't not set schedules of subscription.
I just tried newly, and error occur. req_pvoTtghfVvt0U4

still token
#

Looking