# A game's start time is left out when the venues disagree on it (https://docs.predictorsdk.com/changelog/2026-11-17-disputed-start-not-published)

2026-11-17 · Fix

A matched game no longer shows one venue's out-of-date start time; when the venues' exact start times are more than 10 minutes apart, scheduled_start is null.

`scheduled_start` on `GET /v1/matching-markets/sports` and its lookup was the earliest exact start any venue published, so a venue that kept a game's old time after the league moved it decided the time the API showed. Colorado at Utah on November 18 is a 10 PM ET game on TNT on the NHL's schedule, and SX Bet and Polymarket US list it there, but Polymarket still had it at 9 PM, and the API said 9 PM. Now, when the venues' exact start times are more than 10 minutes apart, `scheduled_start` is `null`, which already meant "no exact start is known": at least one venue is wrong, and nothing in their records says which. `scheduled_date` still names the day, and the list's order is unchanged. Times within 10 minutes of each other, such as a listed 8:15 PM beside an 8:20 PM kickoff, still publish the earliest. An MLB doubleheader, whose two games share one event, now has no start. On November 17 this applied to three of the 198 games in the default list. The same day, start times began coming from the league's schedule, and this rule became the fallback for a game the league's schedule does not list. No field or parameter changed.