Undoing a synth rack deletion routes track to wrong synth.

I still find the synth rack to be a little buggy and unstable - I've had some bad crashes from turning synths on and off, and tonight I had the weirdest thing happen which had me scratching my head for ages. 
 
I was doing some house cleaning in the rack and deleting unused synths and their related tracks. In the course of this, I accidentally deleted an instance of Kontakt along with its related tracks. Immediately realizing what I'd done, I undid the action. And what happened was this: Sonar restored the tracks and the synth, but it routed both the MIDI track and the audio track to a different synth - an instance of Reaktor. 
 
Correct me if I'm wrong, but when you delete a synth and it's associated tracks and then undo that action, you should get back to where you were, no? The tracks should be routed to the same synth. 
 
I could half understand what was happening if the tracks were routed to the first synth in the rack when I undid the deletion, as a kind of "default" routing. But the synth they were routed to is #8 in the list. It just seems so random and arbitrary. As an experiment I tried deleting another synth with its tracks and undoing it - lo and behold the tracks were routed to the same instance of Reaktor as well. Has anyone else experienced this? Is it a bug? I'm going to try and reproduce it in a fresh project. 

OK so here's the recipe if anyone wants to check it out to see what I mean:
 
1) Insert two synths with associated audio/MIDI tracks. For the purposes of this recipe, I used SI-Bass and SI-Electric Piano. 
2) In the synth rack, delete the first synth (in this case SI-Bass) and its associate tracks.
3) Undo this action
 
The deleted synth and its tracks reappear, but the tracks are routed to the other synth (in this case SI-Electric Piano). Anyone else?

Confirmed. This is because undo doesn't restore the order of the list in the output field correctly, isn't it?

Jekyll Vance
I confirm. The bug is probably connected with instrument tracks. When I use separate midi+audio tracks for synth everything works normally.

It's not limited to instrument tracks at my end. However, it does seem to be related to the position of the synth in the rack in a way that I haven't yet explored. For instance, in my recipe above if you delete and undo the second synth, it works properly.

There is no reason why the synth state should not be part of the undo/redo logic (it is just a blob of binary data to the host). Therefore deleting a synth and all of its associated tracks and then undoing should work as expected. The host should restore the synth state from the binary blob saved in the undo/redo stack, and also be able to restore all off the original routing.
 
When you load an existing project, the exact same thing happens: The host loads new instances of all plugins in the project and then sets their state from the binary blobs that were also saved in the project file.
 
I see no reason why delete/undo cannot work as expected. This is definitely a bug.

For better or worse, I have adopted the habit over the years of saving projects in stages (with descriptive names) and have inherent distrust in every scenario being tried/tested in development. Prior to major changes (especially destructive ones), I will save just in case, then can just close the project without a save and reopen it.
 
I realize this may rub some the wrong way, but reliance on "bug free" software (anywhere) is folly.
 
 

I think it's reasonable to assume that an "undo delete synth" command would put the track back the way it was. Are there other things that won't "undo"? I can't remember reading about it in the manual, or seeing it in any of the tutorial videos about the synth rack that I've watched.
Guess you will have to be a little more careful about synth deletion in the future sharke, certainly until Cakewalk can fix the issue. Or if they don't/can't, then a change of workflow is the only option.
Thanks for posting this, it's something I can at least understand when and if it happens to me.

My view it's a bug and should be reported via cake problem reporter (please let us know the number).,Why is it a bug? Because undo does not undo correctly. If it was incapable it should not undo at all or it should produce a warning telling the user that it won't fully undo.