Jeef

Looks like @bdraco we need to turn down the request rate. I’ll follow up again with flume for better details Sent from my iPhoneOn Nov 4, 2022, at 3:15 PM,...

And ideally scale the rate against number of devices so those will 1 flume can get a faster response maybe Sent from my iPhoneOn Nov 4, 2022, at 3:15 PM,...

Relevant Info: https://flumetech.readme.io/docs/rate-limiting >Currently personal clients are allowed 120 requests per hour to our API. Once you have gone over the limit you will get a 429 rate limit error....

Ok so pulling up the code here is what our current settings are: - Notifications are pulled once per minute (one endpoint per user) 1 / minute - Device Data...

So here is where I'm confused. - 120 requests per endpoint per hour - You should I think be hitting 4 end points ... and then only seeing about 30...

I'll get a patch out soon. Got some info from flume which is the /users endpoint gets 120 hits an hour

I'm going to do some tests locally -> changing my poll rate to 10 seconds... should time me out pretty soon I'd think.

 I'll have to restart this in an hour or so but it looks like it timed out after about 146 calls... (however my normal flume integration was previously running...

So I re-ran this with a clean (nothing touch flume) setup:  Which kind of looks like I got about 339 calls before it timed out... In any case I...

so you do a `carthage update --no-build` -- delete schemes followed by a ``carthage build` ?