Matches API "suggested_play_order" returns null
A few years ago this feature was added see (https://feedback.challonge.com/forums/44455-feature-requests/suggestions/11659590-front-end-ui-match-identifier-does-not-match-api-m)
However since the pandemic the value "suggested-play-order" on matches has been returning null making it very difficult to coordinate matches with the front end UI.
-
alexiaamber commented
It's definitely challenging to keep match coordination in sync with the front-end UI when the "suggested-play-order" value on matches returns null. https://uspstrackingnumber.co/
-
Eduardo commented
This bug seems to be fixed at some moment between September 4th 2022 and October 1st 2022. Tournaments created before these dates remain with this value null, but new tournaments initiated in October have the suggested_play_order correctly populated. This issue looks like it's resolved.
I would like some type of feedback or message from the Challonge team addressing this, though. -
Eduardo commented
I noticed this back in August 2021. On July 25, 2021, API was working fine. Then on August 07, 2021, the API returned null values after starting a tournament and I couldn't select a match in my app. I was obligated to print the matches array in a window and select by the index of the array, which is a bit cumbersome.
-
ThePooN commented
I just encountered this as well. You need to enable predictions before clicking "start tournament" to populate "suggested_play_order".