#binh
1 messages · Page 1 of 1 (latest)
Can you share your question?
in the response, I noticed that the schedule is null
"quantity": 1,
"schedule": null,
"start_date": 1678153943,
"status": "active",
"test_clock": null,
"transfer_data": null,
"trial_end": 1681344119,
"trial_settings": {
"end_behavior": {
"missing_payment_method": "create_invoice"
}
},
"trial_start": 1680832343
Can you share why you expect it not be null? Do you use subscription schedule?
in our stripe dashboard the schedule_id does exist from the event
/post/v1/subscription_schedules
Can you share the subscription ID (sub_xxx)?
"id": "sub_sched_1MkyT5LBDgrs2MW8BWLEHqqn",
"from_subscription": "sub_1MiphTLBDgrs2MW8w3a9o2IR"
v1/subscriptions/sub_1MiphTLBDgrs2MW8w3a9o2IR -> "schedule": null,
as for this case:
v1/subscriptions/sub_1Mk0AhLBDgrs2MW8pJFGlqLC -> "schedule":"sub_sched_1MnfFNLBDgrs2MW8tDvLv2kB"
we noticed this behavior of nulls on subscription prior to march 8th
how do we go about rectifying the subscriptions prior to march 8th?
In sub_1MiphTLBDgrs2MW8w3a9o2IR, the subscription schedule has been completed and released. If the subscription schedule is released, it will not be present under schedule parameter
if you look at POST /v1/subscription_schedules/sub_sched_1MkyT5LBDgrs2MW8BWLEHqqn
we've broken it down into 3 phases
so it's not completed
The subscription schedule has 3 phases and the last phase ended at 2023-05-13 00:01:59 UTC.
In https://dashboard.stripe.com/logs/req_sejOrN1hDZoTKa,
The last phase has start_date with 1681344119 (2023-04-13 00:01:59 UTC) which ended at 2023-05-13 00:01:59 UTC
ok, understood. let me get another sample where this is not the case
Sure
subscription_id = sub_1MdsVLLBDgrs2MW8mEHGZQsx
"quantity": 1,
"schedule": null,
"start_date": 1676973083,
"status": "active",
"test_clock": null,
"transfer_data": null,
"trial_end": 1679961719,
"trial_settings": {
"end_behavior": {
"missing_payment_method": "create_invoice"
}
},
"trial_start": 1679392283
}%
"from_subscription": "sub_1MdsVLLBDgrs2MW8mEHGZQsx" -> "id": "sub_sched_1Mg449LBDgrs2MW8XSL8xOGj",
The subscription schedule (sub_sched_1Mg449LBDgrs2MW8XSL8xOGj) belonged to this subscription was released on 2023-04-28 00:01:59.
The last phase has start_date with 1679961719 (2023-03-28 00:01:59 UTC) that ended on 2023-04-28 00:01:59 UTC in https://dashboard.stripe.com/logs/req_avl7E3A2C3KPwO
Once the subscription schedule on a subscription is released, it won't be present in schedule parameter
What are you trying to achieve? Once the subscription schedule is completed, why do you still need the schedule field?
it's recurring, it is not completed until cancel
What is your use case with schedule field then? It doesn't sound like schedule is needed