#ericlim-sub-error

1 messages · Page 1 of 1 (latest)

winter relic
tacit smelt
#

req_ty6bYnMXekwd8B

winter relic
tacit smelt
#

I don't understand your answer. I'm not updating the schedule but subscription in this case.

#

Shouldn't updating subscription be successful when the attached schedules are released?

winter relic
#

You can't directly update the subscription when using the SubscriptionSchedule

tacit smelt
#

I can't update subscription even when the schedules are released, cancelled, or completed?

winter relic
#

That sounds correct, however, let me test this in my test environment

tacit smelt
#

Does that imply I won't be able to call the update subscription API once subscription has associated schedule?

winter relic
#

That is accurate, I just tested this on my end

tacit smelt
#

That is weird. Coz we can currently call update subscription API for a sub with the subscription schedules attached to it as long as the schedules are released. It only failed to update the subscription for this particular request

#

Let me find an example of successful requests

tacit smelt
#

sorry it took some time.

#

req_zIPIqC7ztYOFDa was successful which was updating the subscription sub_1LAiz9E91MHwtTCLOL7v7r5x

#

The sub had a schedule sub_sched_1LAj0RE91MHwtTCLqkuYLwR5

#

somehow when I look at this subscription, the schedule is null..

#

it makes me think if we're not using the phases correctly,,

long compass
#

Not sure I follow

tacit smelt
#

I'm trying to understand when a schedule is no longer associated with a subscription after it's been created.

long compass
#

after the last cycle of the last phase expires and then it's released

tacit smelt
#

Think I get where we've gone wrong with the schedule API. We have not set the end date for the phase and call the release schedule API in a hope that it'd unlink the schedule from the subscription

#

we'll do some more diggings on our end and ask questions if needed.

#

Thanks guys!