I’m not quite sure yet what it took to cause this (hopefully fixed) error, but it may have been from having a late evening forecast run followed by an early morning one, and maybe only in certain time zones. Of course, I want to know if the new version works even for people who didn’t have the error! 
Tom