Reuben

[arctic socket]

@hard wind

here

[hard wind]

Awesome. Sorry for the delay. I can share exact steps. They are: (a) setup a test clock and test customer. (b) create a subscription for the test customer. (c) advance the test clock forward (either to 3 days before the end of billing period or to the end of the billing period). Note that no invoice.upcoming event is emitted

[arctic socket]

No worries, testing it

[hard wind]

Thank you!

[arctic socket]

I'm getting invoice.upcoming event. Are yo listening to this event in test mode?

[hard wind]

to clarify, what do you mean by listening to it? If you mean are we receiving it in our webhook? then yes.

Maybe if you're seeing it, I"ll try again on my end. Perhaps there is something subtle that I am doing to cause it to not show up

[arctic socket]

I get this event every time

[hard wind]

In your test environment, what is the number of days prior to the end of the billing period that is configured for the invoice.upcoming event to be emitted?

[arctic socket]

I have it at the end of the billing period as you suggested

I do not think it would have any effect, but could you try not making an explicit requests to update the subscription, https://dashboard.stripe.com/test/logs/req_HbF2DWrmGEL7RN and https://dashboard.stripe.com/test/logs/req_LzOeakBIHe1BJ9? I would try to run the simplest Test clock as a next step and try to rule things out since I cannot reproduce this on my end.