This topic was automatically generated from Slack. You can find the original thread here.
I have set up the Brillium app, and while the Test Connection button in the connection setup returns a 429 error, when I test a list_assessments step, it appears to work, in that it does not give an error. It does not, however, return any assessments, even though there are 233 of them, and it does the same thing even if I give it a known-incorrect workspace ID. As the screenshot shows, however, despite not reporting an error, the status is still 429 / Too Many Requests. I can do this in Postman just fine, so I don’t think 429 is the correct error, at least not as far as our Brillium rate limit should be concerned.
Hi , I believe this error is thrown from the Brillium side. I tested and it works fine on my side (I only have 4 assessments though)
The reason why your Postman didn’t throw 429 error maybe because Brillium rate limit based on backend identity (.i.e by IP address or similar means). Pipedream backend is a different backend from your local machine, so you may not get the same result as Pipedream.
To investigate this further, would you mind sharing more information as below:
• Are you just testing on the Workflow Builder, or having it running live?
• How many time that your workflow has been executed?
• Could you try to set the Page Size to maybe 250 to see if it fix the issue?
