#DeliveryTiem
1 messages · Page 1 of 1 (latest)
Hi, can you share the subscription creation request id with me where you're seeing this behavior? Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
Hi pgskc, yeah it's ID is req_1Ndxwbto0S1cmm
Can't understand where it's getting it from, we don't have the infrastructure to handle schedules on production yet but somehow they're popping up
Can you share the subscription schedule id with me?
I think the reason here is because you're backdating this subscription, https://stripe.com/docs/api/subscriptions/create#create_subscription-backdate_start_date. Testing it now on my end to confirm
Fair but I don't see any logs connected to the subscription that have this property defined
This subscription schedule was triggered because you used the Dashboard. If you use the API, it would not be the case, https://stripe.com/docs/api/subscriptions/create#create_subscription-backdate_start_date.
So just to make sure we're both thinking the same thing, any subscription update via the dashboard associates a schedule?
When I tested this in the Dashboard, yes. With Dashboard functionalities, I'm unable to assist. Our support team will be able to assist you better than I can: https://support.stripe.com/contact. I'm happy to help with our API/ integration questions you may have.
Most Dashboard changes won't create a Schedule no. Some will, it depends what you are trying to do. So if you team uses the Dashboard to make Subscription updates, your code needs to be resilient to SubscriptionSchedules being created/controlling those Subscriptions in some cases
Yeah i'm seeing a pattern now, 'cancel_at' dates were set and it's triggered a schedule creation.
Okay it's a matter of updating to subscription schedules
Thanks for the info
We're closing this channel now for the weekend. If you have any further questions, we're happy to help next week.
Cool, all the best enjoy the weekend