We just had the same thing happen to us, though as far as we can tell nobody programmed anything strange (like entering an impossible time) when it happened. I can't send a show file, unfortunately, because we fixed the problem and saved over the file before I saw this post, but if it happens again I'll send an email to support with a show file link.
For what it's worth, our "fix" was moving our control cues to a new layer, and re-making the control cues that were acting strange. Also, for reference, here's our build:
WATCHOUT 6.2.1
Windows 7 SP1
ASUS X99-A Intel Motherboard
Intel Core i7-5820k processor
AMD FirePRo W7100 Graphics
G.SKILL Ripjaws V series 16gb (4x4Gb) RAM
