#vijju

1 messages · Page 1 of 1 (latest)

uncut ospreyBOT
lilac beacon
#

Hi 👋 can you share the ID of the Subscription Schedule that you're using for testing?

bleak raven
#

sub_sched_1NH4wbInWjFiBg71hz8wrIJj

lilac beacon
#

Thank you, taking a look

#

Looking at the timestamp that you provided, it does look like a Subscription should have already been created for this Schedule. It's possible our processes in test mode have fallen a bit behind, is this the first time you're seeing this behavior?

bleak raven
#

i observed this time only

#

what i did is i created 60 schedules at the same time

lilac beacon
#

Have any of them created a Subscription yet?

bleak raven
#

nope

lilac beacon
#

Hm, nothing is jumping out at me so far. The Customer you're using for this isn't part of a Test Clock simulation is it?

uncut ospreyBOT
lilac beacon
#

I just checked again and see that there is now a Subscription associated with the Subscription Schedule that you shared.

bleak raven
#

customer is not in test clock
i will also check once
whether it is started for all the 60

bleak raven
#

i've checked it out of 60 only 12 are paid
remaining are in draft
will it be the same case in live mode
if i create a 1000 schedules which start at same time
invoice generation and invoice finalising cant be in at same time
there will some delay right?

young sage
#

There shouldn't be much of a delay in live mode

#

Sometimes there is in test mode though

bleak raven
#

lets say i scheduled 100 subscription which start at 9:10 pm IST today
so at exact 9:10 pm it will create invoices for all the schedules
and after one hour at exact one hour it will finalise the invoices

why i'm asking about this is
we have a scenario
where more than 1000 schedules will start at same time and we want to know if stripe sends invoice.paid events of 1000 at the exact time
then how our server should handle all those events

young sage
#

We would send an invoice.paid event for a given invoice shortly after it's paid

#

So if you have 1000 invoices being paid at the same time, then your webhook endpoint would receive those events in close proximity to each other

#

You'd need to be able to handle this

#

Note that if your endpoint starts rejecting requests due to high load, we do have automatic webhook retries

#

With exponential backoff

bleak raven
#

ok
got it thanks

young sage
#

No problem