#anthonyg-subscription-schedule

1 messages · Page 1 of 1 (latest)

full belfry
#

Do you have a request ID from when you made this request?

#

It sounds like you are manually defining this array and started at an index of 1 instead of 0

lethal shale
#

Yeah, I think I am. If there's a way to do it so that I just define the phase I want to update with just the params I want changed that'd be great. Where do I find the request ID again?

full belfry
#

It will be the Request-ID header that you get back or you can check your Dashboard logs

lethal shale
#

req_2NZW0ugjEBIa3z

pine hare
#

@full belfry I got that one

#

the channel is busy and I've been working with @lethal shale for a while now

lethal shale
#

Soooo, does that mean no help here or that @pine hare is taking over this question?

pine hare
#

I'm taking over

#

there are 14 threads in parallel, that's too much for one person :p

lethal shale
#

Oh shoot, he's busy!

#

So what's the scoop with schedule updates. Can I not just specify which phase and which params I want to update? Seemed like I needed to supply all phases before the one I wanted to update from the error, or something.

pine hare
#

correct you have to re-supply all current and future phases

#

we don't support updating just one specific phase

#

it's one of the things that make schedules really really complex to use unfortunately 😦

lethal shale
#

And what params for each phase are required? It's not totally clear to me from the docs.

pine hare
#

That call is a complete override

#

we forget everything about the schedule, we replace every phase with what you pass. So you don't pass what changes, you re-pass everything as if you were creating the schedule right now

lethal shale
#

Ok, so basically take all the params returned by a call to get the schedule and then just update the ones you want changed or added from there?

pine hare
#

well it's important to remember that a GET returns a resource this has properties and the properties on a phase are not 1:1 with the parameters on that API

#

so no, you don't just take all the returned arrays of hashes and change some params, you have to basically keep track of all your phase, and re-pass them cleanly

#

it really is this complex

lethal shale
#

Hey can I not add a trial to a schedule phase from the dashboard?

#

I'm seeing only a way to change the schedule date of a phase or to pause payment collection. But not sure if either of those is what I want for a handful of customers I have to delay billing on before 5PM CST here today. I just want to delay their next payment on a monthly plan to bill on Nov 15th this month.

#

They are set to bill today, but I want to simply delay them till the 15th, then have them resume the regular schedule which is every month on the 3rd.

pine hare
#

I ~never use the Dashboard so not sure. It's plausible you have to cancel the schedule and recreate them

lethal shale
#

Yeah, the dashboard is so inconsistent compared to the api. There are major pieces missing from functionality with it. Real pain for doing one off adjustments needed that don't make sense to do from the api.