Serious fault with API. Left for over two days unattended.

This has now been an issue for over 48 hours.

Team matches not accessible via API.

Could it be prioritised please.

Example

https://api.chess.com/pub/club/norfolk-knights/matches

{"code":0,"message":"An internal error has occurred. Please contact Chess.com Developer's Forum for further help https://www.chess.com/club/chess-com-developer-community ."}

Oh, dear!

Devs have a ticket about it.

Good. But after three days I would have hoped that some progress had been made. And the only suggestion I got from support was to post in the Developer Community group. Wish I'd thought of that.

Tickets get prioritized and it's very likely that the other tickers and projects are higher priority.

Tickets with higher priority than fixing what's broken? Must be important then.

Now into day 4

Why are you posting this here? It doesn't seem to be relevent to the posted API bug.

+1 please prioritize this as it affects a number of us!

If we assume this problem began five days ago (28th./July?) ....

Still not fixed - Day: 5

At my job we have a horn blowing and lights flashing every time a new ticket arrives. Just to make sure we stop whatever we are doing and fix the ticket first...

Still not fixed - Day: 6

I mean it's an API that isn't integral to the site operations and other projects for the site likely take priority.

That's understandable, particularly where members are using the API for purely personal reasons, but perhaps staff/developers might take into account the contribution to the site that the organisers of the various leagues make?

The WL, EL, 1WL, The Asia League, TMCL, TMCL960 and Knockout, to mention just a few, surely add to the attractiveness of the site? I'm involved in two of those leagues and frankly, if I wasn't able to pull down all the match and related data that I can at present, I doubt that I'd continue to help with them because so much more of my time would be demanded.

Still not fixed - Day: 7

Hey, guys. I'll see what's going on. Sounds like this wasn't prioritized properly. The API is considered critical functionality because it supports a significant player community, and I think that the scope of this bug was missing. I'll see what's what.

@Martin_Stahl feel free to share ticket numbers with our Developer Club. That way when they contact Support or write in the forums we can all reference the same thing.

Thanks Ben

Should be fine, now.

That's reassuring to hear but it's taken nine full days to fix this. If I'm unable to access match data at the time I'm trying to compile my league's results, we're sunk because the manual alternative takes hours and hours.

But are 'ticket numbers' still used? I haven't been given one of those in many years and they were useful because they enabled everyone involved to reference the specific complaint or problem involved.
I remember at least one recent bug report I submitted that got 'lost in the machinery' because (I think) the staff member reviewing it mistakenly thought it related to a different problem that had already been resolved.

That's to say, if we can have ticket numbers back I'd be most grateful.  😊

All we need now is for the most recent 500 finished matches problem to be fixed?

Well, don't forget the 500 error when trying to query the list of players from large countries like USA