#arvindkks-schedule
1 messages · Page 1 of 1 (latest)
@frigid lava you use the Subscription Schedule API so it creates a Schedule, that's expected. What's the problem?
If I set the phase.start_date to current timestamp or a timestamp in the past it creates a subscription instead
if I set the phase.start_date to the future it creates a schedule
This makes sense and this is what I expect to happen, and this is what is happening currently also.
Except for this one instant : https://dashboard.stripe.com/test/logs/req_hvLVZZSRAPXCyW
It would be great if you can check the details of this particular API call, which created a schedule instead of subscription
Just to clarify: the request always creates a Schedule. You ask is: why didn't it also create and start the Subscription immediately?
yes
Because your phase start is 1638276093 which is November 30
sure!
Sorry wrong link can you check this - https://dashboard.stripe.com/test/logs/req_CHMNFGsMQKlU9G
@steady iris can you please check this API request instead
sure, please give me sometimes, there are 16 other people asking questions right now
@frigid lava I think it's just bad luck, you sent 1635684098 but the request was made that the 1635684097 second
so it looked like you wanted to start a second in the future
https://stripe.com/docs/api/subscription_schedules/create#create_subscription_schedule-start_date use start_date: "now" instead
Thank you @steady iris
sure let me know if that unblocks you!