Mix Recall suddenly declaring certain sends "dead," help please

 
Hi all,
Yesterday I saved four mix scenes using Mix recall. Among other things, they involve the vocal track's output being set to None, and a pre-fader send from the vocal track to a vocal bus, which feeds the Master bus. No big deal. I rendered each mix to a wav file, and all worked fine.
 
Today I launched Sonar to find that when recalling any one of these mixes, the vocal is not heard, apparently because, for some reason, in the console view, the name of the vocal bus in the little send assign window is grayed out, and no signal is sent to the vocal bus.
 
I have no idea why, I certainly didn't do that, nor was it that way when last saving the project.
 
I can't seem to restore the send to life of any kind. Sonar lets me choose other destination busses, but they too will be grayed out in the little send-name window after being chosen, and they don't send signal anywhere.
 
The only workaround I've found is to create a new vocal bus 2, move to it all the FX from the vocal bus 1 FX rack, insert a new send from the vocal track to vocal bus 2, and delete the grayed out send and the original vocal bus.
 
This workaround only takes a few moments and around 20-25 extra mouse-clicks per dud send, now that I spent, oh, 45 minutes discovering, testing and now describing it... now, what was that riff in my head I'd wanted to get down? Escapes me, silly me, oh well, it's late. Enough play for one day.
 
Has this happened to anyone, especially in Sonar Hopkinton by chance? Is there something I'm overlooking? Please say yes. All my drivers etc are up to date etc etc,  this is literally happening from one day to the next. I can't imagine this is supposed to work this way. When I upgraded from to Platinum to get Mix Recall, it was to make recalling mixes easy, not extra work and puzzlement.
 
If I can't crack this I'll have to stick to old-fashioned versioning, and ponder the benefits of new killer features which I mistrust. 

brundlefly
 
 
Sounds like the send is just turned off. Hover over the send, and click the 'power' button on the left side to re-activate it.

Thanks. Ok, that was my introduction to the button which appears when you mouse over it. Guess I should have remembered it from a video or something I've read. Anyways, that is helpful; switching the send back on does restore the signal.
 
But the real questions for me are
--why does the mix recall switch it off to begin with?
-- Again, is this how it is supposed to work? That would blow my mind. Leaving out a send?
 
The point of mix recall is to switch between entire mixes -- total recall, if all options are checked (they are) -- not randomised partial recall.
 
I'm having to remember how something sounded, and correct the preset? WTF. Imagine if FX presets worked that way.
 
In this case I was lucky because I was returning to the project the next day, and because the self-switched-off send happened to be the only source of vocal signal, so I knew right away something was wrong.
 
But -- unless I can get a clear remedy  either here, or if need be, by submitting a support ticket -- then this behavior is so random, I have no idea whether / how it will strike next. That makes me a Nervous Nellie. What if it this happens to a send (or sends) for something less noticeable, returned to a month later? Seems like the only way to be sure Mix Recall has correctly recalled would be to open the version in which I saved that mix recall preset (I always indicate this is file names) and compare, but ...
 -- this completely defeats the purpose of Mix Recall, which is to save you from having to open different file versions to compare mixes. 
-- what a proper PITA; I just won't do it. 
 
Has anyone else seen this or other holes in Mix Recall's memory?
 
Does anyone have any advice on how to prevent this? 
 
Pretty please?
 
[Transition to full-on rant:] 
 
Between this and the automation ghosts-in-the-machine I've been seeing -- the ones that my antibiotic of last resort, renaming aud.ini, no longer seems to fix reliably -- I'm getting increasingly unwilling to trust Sonar (yes, ymmv, to be clear, dutifully spoken, I can only Sonar on my machine -- on my kind of expensive, custom-made-for-music laptop from a vendor recommended by one of the Sound On Sound editors, and which handles other DAWs with far fewer problems, that machine) I think, after a year of plugging away, I will have to shelve the idea of Sonar as my Mother Ship DAW. For some things which are important to me, like comping / melodyne workflow, it can't be beat, and so for those Sonar can be my deluxe stem creator of choice. 
 
But for mixing -- man, if  automation, and related metadata, like presets which include automation settings, don't stick --  I don't see the point. Computers are supposed to do the remembering for you. If it mocks my efforts and wastes my creative time, this DAW becomes no longer worth studying.  Sort of becomes the pseudoscience of itself after a while. 
 
[Rant endeth]
 
 
 

Anderton
Any chance you don't know about the Mix Recall Settings advanced options menu?

Fair question -- I still get tripped up by the basics sometime -- including forgetting to plug my cans in, then wondering why there's no sound ... But in this, case, I'm sorry to say, I'd not overlooked those setting, Craig. (I wish I could say I'd had, and missed something basic.) I watched the vids and read all the official Mix Recall documentation, and checked out those advanced settings, before ever trying Mix Recall.  In this case, all the items were checked (as they should have been).
 
At all events, I don't see any advanced settings item which would cause a send to be switched off, even if the item were not checked.
 
It's worked correctly loads of times, I did nothing different this time. I'm really at a loss here....  Am I the only one to see anything like this?