John, I don't think that is the case. I think I've been able to root cause it back to the Runtime. When logged in to Runtime via Remote Desktop Connection I can witness the bot navigation actions work as desired. However, when I""m not RDC to the VM it's a hit and miss. Is it possible that the Runtime had not been correctly setup? Runtime possibly logging it's out after inactivity?
Thank you,
Chris