Attack start time becomes delayed

[MagooNZ]

I have noticed this quite a few times. Usually occurs when a major offensive is underway. Without noticing the attack start time, the program appears to randomly change the attack start time to something more than several months or even a year into the future. Once this affects the start of one attack, all subsequent attacks also get the wrong start time. Of course once I noticed that my attacks didn't start, I have to go through all of them, cancel them, and reset to the normal minimal time delay of just a few hours.
Perhaps I am clicking the mouse button too fast and something goes wrong? Perhaps I accidentally clicked a unit to move it a long way, then cancelled it, but the program remembered the travel time and set this as the new attack delay time?

 

[Pang Bingxun]

It sounds like by accident you set the starting date to somewhen in the not so soon future and kept it as starting date. It happened to me, too. A true bug causing something like this is unknown to me.

 

[Mr_B0narpte]

I've had the bug where units say "the mission has commenced" (or words to that effect), but it's not doing anything. But cancelling the mission and re-ordering it typically fixes it for me.

 

[MagooNZ]

I've had the bug where units say "the mission has commenced" (or words to that effect), but it's not doing anything. But cancelling the mission and re-ordering it typically fixes it for me.

I don't recall seeing this version, but I will try to replicate my original problem to identify the key strokes & mouse clicks that cause it.