Any chance that some of this (re-)scheduling took place between 5/25 and 6/1? There were some known issues with guide data ingestion which manifested with symptoms such as you describe. It has since been corrected but, as described in the linked thread, required deletion of any recording jobs created during that timeframe and subsequently creating them again.
