It backs up every night, so I already have last nights. But, reading this "failed to load routines: "no body"" · Issue #191 · 586837r/node-red-contrib-alexa-remote2 · GitHub I think it may be you do have to completely remove the remote2, and start afresh with it 
I'm going to try this approach.
I was getting the same error message and it appears to work now but your setup is a lot more sophisticated than mine I think.
Everything (well a lot of things) are run via routines and specific phrases in Device Activity, I see nothing in any debug node, its like they have all gone deaf 
Even after the restore? Does your authfile exist? Even with the routines issue I still had "Device Activity" functionality..
I've not gone down the restore path as yet, I don't know when it started to be honest, and I maintain the last 10 days. I'm trying the method of removing all, then do it clean and re-import the flows. Fingers crossed!!
Ok, well the device activity part has been screwed by Amazon, so if yours is working I wouldn't change anything
Yikes maybe it's headed my way.. but so far it's still working - just added a debug to my "device activity" node and asked Alexa what the weather was and the results are there.
Very lucky indeed, don't touch a thing 
I was thinking it may just be a UK thing, but I don't think so reading the posts.
Reading the initial post, the Dev isn't answering, which isn't good, but someone has forked it, but I don't really see what the changes are. So I'm not changing it again for now. I'll just have to go back to the old method, and keep my hopes up.
Did you ever create an authfile? Maybe that has something to do with it?
Its configured to create one, although I've never actually created one. I've had it like this since the beginning. But not had these issues until yesterday, which is when Amazon started deactivating APIs it appears.
I guess it's probably a cloud zone thing then.. and it will happen to me at some point - sigh. Yet again more reasons why to be wary of any cloud service.
I did manually create my authfile a while ago so maybe try that..
I just noticed that someone got it working in that thread you posted..
I'm not sure I agree with manually deleting some Remote2 node subdirectories - seems kinda dangerous to NR stability but whatevah.
If you remove from the CLI like I did without touching anything else I think the "cakebaked" version works as it contains the updated connections stuff.
Bummer I'm getting this which I don't think is a local issue
npm ERR! enoent spawn git ENOENT
npm ERR! enoent This is related to npm not being able to find a file.
** Ahh. I think you actually need the remote2 installed when run, I no longer have it.
Ok, so here goes again 
I got there thanks to that thread, man that was a long haul.
So what is the consensus, worth upgrading to cakebaked? Fortunately, my on device activity nodes with remote2 are still working somehow, knock on wood, but if it breaks does cakebaked work out of the box or do you also have to install the fixed library in that github issue thread?
I dunno - I did the CLI upgrade thing to cakebaked and then ran a few tests, things seem to be working. I was getting the same error that @Royski was on every Deploy and now all good. will report back if I notice any issues.
TBH I wouldn't upgrade anything right now.
Although I've been able to get Alexa-remote2 working again, I have a knock on effect with other nodes which I'm trying to track down.
At this rate, my quickest solution may be to reinstall NR 
If you are to upgrade, then I would follow these instructions 
Jeez you send me down the cakebaked route and now abandon me... 
I can probably restore it the same way.. if needed.
I just did this and so far so good. Might want to add to that post that you need to restart NR to see changes though.
Edited the prior post! Thanks..
