#ric-subscription-invoice
abstract harness
Do you have an example subscription ID I can take a look at?
quaint aurora
Hi hanzo. Subscription ID is sub_1NcqkZCqGYqrCJZ6sOdY4V1F
That O in the middle could be a 0
It has an upcoming invoice, but it hasn't created it or sent the webhook yet
abstract harness
If you don't set the billing cycle anchor, does that generate an invoice?
quaint aurora
I'm not sure... I've always set the anchor, but I did recently switch from the current time + 30 seconds, to the current tome + 3 seconds. And I've no idea why it was set to 30 before...?
The anchor is in there because it'll, eventually, be possible for some scenarios to need billing to start in a few days time. So the anchor for those will be inline with that
mystic mantleBOT
quaint aurora
Invoice just created itself now I think
Yep, the webhook has come through. 31 minutes delay though... surely not normal?
There's been a few cases where it's taken a couple of minutes, I was hoping removing the 30 seconds from the anchor would resolve that, but I've never seen it take this long before
uneven garden
ric-subscription-invoice
@quaint aurora absolutely normal, it's all done async in the background, sometimes there's a delay. There's not really a guarantee any of this will happen instantly
quaint aurora
OK. What's the longest most likely delay we'd be looking at for these?
Just need to make sure the service is well worded before any of this goes live and people try to use it...
uneven garden
Hours of delays in production are totally normal. Remember this is a completely asynchronous process around Invoices renewals and Invoices payments. None of it is up to the hour.