Last night I had a programme running and it errored on the first call to the badges/name endpoint on the API, exact API endpoint call:

https://api.stackexchange.com/2.2/badges/name?order=asc&sort=rank&site=stackoverflow&pagesize=100&page=1

Response:

{"error_id":500,"error_message":"this error has been logged","error_name":"internal_error"}

First occurrence: approximately 00:00UTC+00:00
Most recent occurrence: 06:17UTC+00:00

Update: this is back, has been happening for several days for me now, latest at 00:05UTC+00:00 on 18 January 2017. This only happens when I set pagesize=100.

Verified with and without application key. Verified from three independent IP addresses (and computers).

API docs recommend posting a question on Stack Apps, so here it is.

  • 2
    Confirmed. Setting either the pagesize parameter, or page > 1, seems to trigger the bug. – Brock Adams Oct 5 '16 at 7:15
  • @BrockAdams Thanks for investigating that! I was attempting to, but I kept getting a throttle_violation and gave up. – 202_accepted Oct 5 '16 at 7:18
  • @BrockAdams This issue is back. – 202_accepted Jan 18 '17 at 6:07
  • Huh? I didn't know it was ever not back. ;) Anywho, an SE developer will have to fix this. – Brock Adams Jan 18 '17 at 6:12
  • @BrockAdams It got fixed last time shortly after reported here, which was still multiple days after it started. – 202_accepted Jan 18 '17 at 6:15
  • 1
    The first time this happened was around the time that the Not A Robot badge was introduced, this time it's around the time that the Census badge was introduced. Coincidence? – Stijn Jan 20 '17 at 11:16
  • 1
    Per comment of @Oded, this has been fixed. – Stijn Jan 20 '17 at 18:06
up vote 5 down vote accepted

I don't know for sure what the original problem was, but the most recent issue was a result of implementing a new badge without rebuilding the API. Once the API was pushed to production, the bug was resolved. If it happens again (especially if there's a new badge) please let me (or really any employee) know. We can contact a developer directly.


From a comment on a related question:

Fundamentally the problem is that the API can remain broken without us really paying attention to it. I appreciate your report since it prompted us to rebuild the API. (That was the immediate problem this time around.) But we shouldn't really be relying on user reports for this sort of thing.

We need to start treating our products as a platform. We don't treat our API as mission critical. There's good reasons for that, but it's going to hurt us if we don't sort it out eventually. (Summary: sorry about that. We can do better.)

  • I thought your comment made for a better answer. I hope that's okay. – Brock Adams Jan 21 '17 at 10:49

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .