I was working on Blaze and noticed that I was getting quite a few of those nasty backoff violations. I checked my code for infinite loops and whatnot, then checked the dev console.
Here's the timeline:
/answerswith my key and a pagesize of 100. The exact path I call:
I get back a 10 second backoff parameter. On the first call. (I'm not hammering it, this is the first time I opened it today)
- I allow the user to disregard it (because I'm too lazy to build in a backoff checker gizmo) and the API hates me.
I don't really think that calling
/answers should send a backoff on the first time. Sources also say that
/posts does the same thing, but can't be repro'd on
Edit: Upon further testing, it seems I can only repro this behavior when making calls against Stack Overflow.
Another edit: I can repro this on this simple API call in the console - where I'm only asking for the single most recent answer, and I get a 10s backoff on the first try. This can't be right.