This is what I found out about from support. Apparently, if a node goes into unmanage, it ignores any reset trigger actions. I would say this is a serious design flaw, but since it does not appear to have created issues for anyone else, maybe not.
So to summarize, the conversation, even if you have a reset trigger that says to reset when node is unmanaged, there is a hard-coded override that resets the trigger and ignores the alert actions for a reset. I have submitted a feature request to correct this.