#DeliveryTiem

1 messages · Page 1 of 1 (latest)

sharp driftBOT
hidden tangle
pseudo glen
#

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

hidden tangle
#

Can you share the subscription schedule id with me?

pseudo glen
#

Yep will get it now

#

Schedule id is sub_sched_1MHzwaIUwLvVicLY42BgRVkI

hidden tangle
pseudo glen
#

Fair but I don't see any logs connected to the subscription that have this property defined

hidden tangle
pseudo glen
#

So just to make sure we're both thinking the same thing, any subscription update via the dashboard associates a schedule?

hidden tangle
#

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.

versed grove
#

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

pseudo glen
#

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

hidden tangle
#

We're closing this channel now for the weekend. If you have any further questions, we're happy to help next week.

pseudo glen
#

Cool, all the best enjoy the weekend