-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
429 error Rate Limits #81
Comments
@vangstma do you always get this error for any board, or only for boards with lot of cards? I never ran in such an issue, and I do not have a business account |
Hello Vangstma. No matter which Trello account type you have, use of the REST API is restricted by rate limiting and there is no way around it. If you're exporting very large amounts of card data, you're going to have to break your requests down into batches. |
After reducing
The "missing x-trello-user-agent-extension header" message is interesting and might be a key to understanding this. Incidentally, awesome extension and thank you for continuing the development of it. |
Exporting individually doesn't seem to trigger the rate limit as often. |
I never heard of such an header, and actually cannot find much about it, but it sounds interesting! |
@vangstma @sunnyape @codewinch I just pushed a commit for the new version that adds this header to all AJAX calls. I will later publish to the Chrome Web Store, but if you want you can try it by downloading source code and manually installing the extension in Chrome. |
Upgrading to "Business Class" (pay to export personal data!) doesn't resolve the issue. I've also tried wrapping an incrementing 1 second delay (via setTimeout) around the $.ajax call and it did help, but eventually still threw a ton of those messages. (Trying to export about 20 boards.) |
@codewinch this also happens with the new version adding that header? Same errors? |
After the last update of the Atlassian platform. I can't extract any more information, error 429 always appears. How can I correct this?
The text was updated successfully, but these errors were encountered: