You are not the first, and probably not the last to get this message.Its generally a mistake.
It mostly occurs,(possibly not exclusively) at the change over time when impatience and reloading happens ,whilst the computer is still trying to load the new schedule.