#deadshot-testclock-invoice
pale surgeBOT
Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- deadshot7814, 1 day ago, 20 messages
- deadshot-futuresub-webhookevent, 3 days ago, 19 messages
cloud snow
Hi 👋 hm, I was thinking you didn't need to explicitly set that but may be mistaken. Can you share the ID of the Invoice where you saw that message so I can take a closer look at its history?
sly vortex
Here is the invoice ID,
in_1OeJY1HCPH5IrTb7T780PDuA
cloud snow
Thank you, apologies for the delay, taking a look.
sly vortex
np
cloud snow
It's going to take me a second to step through this since there is a test clock involved as well. I'll need to bounce around to other threads but will be back.
sly vortex
Ok, I will be waiting
cloud snow
Some insight into what I'm digging into in case you want to follow along. I need to compare it to the time of the test clock being used, but I see the Subscription was cancelled shortly after the final Invoice was created (again test clocks could be obscuring how far apart those should be). I'm wondering if the Subscription got canceled before the final Invoice could auto-advance, which disables auto-advance for all remaining Invoices for the Subscription.
sly vortex
What was the reason of cancellation? subscription end?
Also subscription ended on Mar 19 and if I remember correctly, I advanced it from Mar 12 to Mar 20.
cloud snow
That was the end_behavior set on the Subscription Schedule, to cancel the associated Subscription at the end of the Subscription Schedule's lifecycle:
https://stripe.com/docs/api/subscription_schedules/create#create_subscription_schedule-end_behavior
sly vortex
Yes, I am creating it with end_behaviour set to cancel. But is that the reason for invoice not auto-advancing?
cloud snow
I don't think so, still trying to spot that
pale surgeBOT
sly vortex
Any update?
cloud snow
Not yet, not spotting anything about the state of the Customer or the Subscription that looks like it would have impacted it. Do you see that behavior consistently if you repeat that flow?
sly vortex
No, I havent tried again, its first time
static wave