Hello @Russ,
I found out what happened. First when I changed my machine name and then the name in the site's control panel, I don't know why, but the commands that were associated with Alexa's app routines lost their link. I think this is what you mentioned that could break TRIGGERcmd. Alexa interpreted the applied command, but did not open the files and applications. But there was an even bigger problem, because Alexa discovered other new commands associated with the other name I gave my machine, i.e the commands in Alexa were duplicated! I had to delete everything one by one it created. After that, I replaced a backup I had of the TRIGGERcmd commands (commands.json file) and let Alexa rediscover all the commands again. But it still couldn't figure out all the commands at once. I had to re-enable Alexa's TRIGGERcmd skill and ask it to find out the rest of the commands. So to finish, I had to reassociate all the commands again for each routine I had. Finally, with this I don't think to change my machine name anytime soon. It was a lot of work, it took me almost 2 hours to redo the process. In case it happens to someone, that can be of support so that no one gets lost at first like I was.
Regards,