Command Processing shows a "Timeout for execution" after successful execution of a command. The cause is mismatching units of the timer ticks read from PC clock on systems running without PC restarts. The issue could also affect the Command Sequencer and network data transmission.
The bug has been fixed. The clock ticks based timeouts are now correctly handled.
To benefit from this fix: