#lafafm

1 messages · Page 1 of 1 (latest)

lapis starBOT
torn pollen
#

Hey there

#

Can you share the request ID for the error?

covert fern
#

Here's a screenshot from logs page

Yellow is a call rate limit call

#

req_x3aCOdaRb7ZVcD

#

My confusion is on 25req/s for a call rate
From the screenshot above it doesn't seem like so

torn pollen
#

Give me a min to take a look at that request

covert fern
#

Thanks

torn pollen
#

Ah okay yeah so there are some specific rate limits on updating Subscriptions. Looks like you did update that Sub several times within a minute.

#

You'll want to check your code to make sure that is expected. If so, you will want to have some retry mechanisms in place.

covert fern
#

It's expected, as that was QA checking some subscription updates

#

It's a manual check, but with a few checks within a minute, I believe

#

Can you tell me a limit for that type of requests?

#

E.g. X / minute?

#

It would help for QA's to eliminate that factor

torn pollen
#

Hmm let me check

#

Okay so overall the values seem to be dynamic but looks like it is 10 Invoices per minute.

#

I think your overall issue here is that you are using a test clock

#

Which is making all your invoices created at the same time.

#

That said, we recommend that you just mock responses here

#

Instead of hitting the actual API

#

And beware that these limits are subject to change

covert fern
#

Hmm

But there were not invoices created during these subscription update calls

Or is it related anyway?

#

And anyway

These limits is per subscription only? Or it combined along multiple / all subscriptions?

torn pollen
#

Yes per Subscription

#

There are some limits on Invoices generated per Sub per minute as well as daily

#

You can see that you have a bunch of Invoices generated the same minute for that Sub

#

That is because of the test clock

#

So it exceeds the 10 limit for a per-minute quota

covert fern
#

Uh

#

Okay, got it

#

Thank you

#

Have a good day 🙂