While sending, addons for signing using web-ext we are getting error response , request was throttled try again in 26175 seconds.
This we are seeing recently.
What is the root cause of the issue.? and what is the limit , how many addons can be signed per account within a given timeframe range.
1 Like
Hi @addons, can you please share the name, GUID, or URL of your extension so we can look into it?
From what you’ve described, it sounds like your extension files are large for the validator to process and the request is timing out. If you can reduce the size of your files that may help.
1 Like
This error is about submitting too many versions for signing. Please limit the number of submissions to the minimum. If you encounter the error message, you have to wait the stated time before you can submit another version.
1 Like
“Request was throttled. Expected available in 2431 seconds.” Seriously? Fix this please. https://addons.mozilla.org/en-US/firefox/addon/christmas-plaid/?utm_source=addons.mozilla.org&utm_medium=referral&utm_content=search
Great, but where we can get description of these time/count limits? Google a lot and searched on all the related mozilla portals, this topic is one super-related seems like. Would like to know how can we increase this limit since our add-ons building is managed automatically and building process can be simply broken by this non-finished operation.
“Request was throttled. Expected available in 85468 seconds.” What?
I’ve got a dozen Firefox add-on tabs open, trying to expedite this process of voting on extensions. I’m sure this developer, like the others, would appreciate a five-star rating. But Mozilla apparently wants to prevent that. I’ve opened the tabs. I can’t hold them open. So maybe I’ll try again in five years, which is about how long it’s been since I last got around to this.
Rate limits are in place on addons.mozilla.org to help combat abuse such as review spam. Currently users cannot submit more than 20 reviews per day. IMO that seems like a reasonable upper limit for the vast majority of users.
Rate limits are not publicly documented, but addons.mozilla.org is an open source project, so you can poke through the repository on GitHub to find the current rate limits. The current add-on submission throttles can be found here.
We do not support per-user rate limit modifications.
The current rate limits are in place to help ensure the integrity of the services we provide; we cannot support every developer submitting a new version every time the main branch of their project receives a commit.
Your best course of action is to modify your build process to only submit new versions of an add-on when you cut a release.
1 Like
I had only submitted a handful. Nowhere near 20.
I see there is also a burst limit 6/minute.
Additionally, if you also leave a written review, that counts as another request.
Also if you change your mind and use a different ranting, it also counts.
I’ve just managed to “use up” all of my ratings for today just by trying to rate a single one of my own addons - which doesn’t even work 
.
Interesting. Thanks for the feedback, @raywood & @juraj.masiar!
Could you share more information about the flow you went through before exhausting your quota? I realize you probably can’t give an exact log, but I think getting a a more detailed account of your experience will help the team understand the issue.
To be more precise, I’ve used up my quota by hitting the rating star multiple times .
So it looks like it works as designed. Although in the ideal world, it would only count unique addon ratings.
Because as I mentioned, if you change your mind and change stars from 4 to 5 and then add a review, this counts as 3 ratings.
Then again, I realize this is an edge case and relaxing quotas could be misused by malicious actors (like in Chrome Web Store).