Becca

[trail field]

hello! to clarify, are you having trouble figuring how to downgrade on a Subscription Schedule?

[fast rain]

no, the schedule itself is working, but notice that between evt_1MW7puJvPV2PodcLZxtmjeAp and evt_1MW8dpJvPV2PodcLAQ8AFY1H the subscription item id has changed

also I've got something weird with this subscription on the test clock

in_1MW8doJvPV2PodcL8xuDjb7g

the test clock is past when it says the invoice will be finalized

[trail field]

hmmm, regarding the Subscription item id, as far as I can tell, there isn't a way to keep the Subscription item id

[fast rain]

unfortunate. I know on subscription_schedule.released I can pull the subscription from the api to get the new item id, but that means there could be overlap with the subsequent invoice.created which will query our database for the entry associated with the item id. and the schedule object you get from creating/updating the schedule doesn't have the item id on it either.

[trail field]

it's a bit odd that it's still stuck in draft, can you try moving the test clock forward another time?

[fast rain]

actually with this iteration, the invoice was created before the schedule is released (not sure if that's always or just the order things are in this time), so yeah my logic for handling that just won't work

yeah sure one sec

aye, moved forward an hour and invoice is finalized

[trail field]

alright great!

[fast rain]

yeah, so now it's just the subscription item id breaking my integration haha

[sonic rain]

Hi @fast rain I'm taking over, let me know if you have any follow-up question

[fast rain]

ah no can archive - I'm working on figuring out how to restructure my integration to handle the item id not being static and putting together a flow document. would it be ok to ask in the chan later for a review of my flow document to see if it makes sense? not necessarily a specific api question so not sure if that'd be appropriate

[sonic rain]

Sure no problem, feel free to reach out when you need help.