You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Under the hood, this is the full error message including the exception:
Could not create user: probably this user already exists but is not present in meta.json 429 Client Error: TOO MANY REQUESTS for url: http://13.228.231.8//api/users?no_invite=1
importing: 365880
I can see this kind of error was expected and this comment shows how this can be fixed: #23 (comment)
However, even after setting RATELIMIT_ENABLED=False in redash (in /opt/redash/env for AWS AMI) I am still getting rate limited with the same message. What did change, however, is how many calls succeeded before getting rate limited. Before disabling RATELIMIT_ENABLED rate limit would kick in after creating 50 users, and after, it would start after creating 100 users.
The text was updated successfully, but these errors were encountered:
@shibacow is correct. The environment variable is called REDASH_RATELIMIT_ENABLED. This is then mapped to a Python constant called RATELIMIT_ENABLED. If you set an environment variable without REDASH_ appended to it, I would not expect this to have any effect.
Under the hood, this is the full error message including the exception:
I can see this kind of error was expected and this comment shows how this can be fixed:
#23 (comment)
However, even after setting
RATELIMIT_ENABLED=False
in redash (in/opt/redash/env
for AWS AMI) I am still getting rate limited with the same message. What did change, however, is how many calls succeeded before getting rate limited. Before disablingRATELIMIT_ENABLED
rate limit would kick in after creating 50 users, and after, it would start after creating 100 users.The text was updated successfully, but these errors were encountered: