Interesting problem. Which particular build (and release) of TRS19 are you using. I have both TRS19 Platinum and TRS 19 SP1 Standard and have not (yet) experienced this in either.
Driver commands are saved as part of the Session data. Is it just the one session that is showing this problem? If it can be reproduced in other sessions and especially in sessions from other routes then it could provide the N3V QA team something to work with.
Over the years I have experienced many such "issues" that cannot be reliably reproduced (or reproduced at all), which makes them extremely difficult to track down and frustrating while waiting. Often they simply disappear seemingly by themselves or after an update.