#Kinno
1 messages · Page 1 of 1 (latest)
Hi
would these even show up there in the first place?
if the request reached to our infrastructures, it should be traced somewhere.
At least you'll have a requestId
that means since there's no failed request for the problematic entity in question
it's either not reaching your infrastructure or we have a sneaky bug somewhere on our side and it's not rate limiting related at all
By logs I specifically was talking about the Developers -> Logs view on the dashboard, could you confirm whether rate limited requests would pop up in there with an error code? This will allow me to rule out our rate limiting handling as a cause and be a great help
correct.
There will be a requestId (req_123) if the API call reached to our infrastructures. You'll see a request with 429.
Right, don't see one there so it's not rate limited. Was hoping that wasn't the case since that was our only lead so far.
Thank you very much for the quick feedback! We'll be able to look into the real cause with greater focus now :)
happy to help!