What's new

How to manually load recovery data?

Is there a way to manually load the most recent autosave/recovery data after a crash? I experienced a crash but got no option to recover my lost work after restarting the software.
 
Navigate to your auto-save folder and open the files from there. Be sure to save them to your working folder after you have them open.
 
Navigate to your auto-save folder and open the files from there. Be sure to save them to your working folder after you have them open.

There is such a thing?

I'd say I need to get out more, but probably need to stay in and find out from reading the help and manual about that stuff (OH, WAIT, Those are not exactly helpful)
 
Weird. I found the folder but it's empty. My autosave interval is set to 5 minutes. o_O

giphy.gif
 
Weird. I found the folder but it's empty. My autosave interval is set to 5 minutes. o_O

It is empty here as well. I have never been asked about autorecover, so ????

I looked, and autorecover is on, everything is set to 8 minutes. I have used Alibre for more than 8 minutes recently, so apparently these recovery files are cleared on exit from Alibre (assuming they are properly saved).

That is interesting, because I have "chronically unsaved files", ones that ask me to save them even if I opened and closed the file with no actions of any sort taken. These files if I open them and go immediately to the "file" menu, have the "save" option active, so the program "thinks" they are unsaved. So, why is there no recovery file present?

However, I opened a file, made a change, did NOT save it, went to task manager and ended the Alibre task. Disturbingly, I could do that with just one click and no confirmation.... But in any case, ther is now a recover file, so it works.

I still do not know why the files that apparently have the "I'm not saved" flag do NOT generate a recovery file, even though they demand to be saved when closed..
 
Well, it didn't generate recovery data when it crashed for me. ;)

Seems kind of strange that such data would only be generated when the software detects a problem. You would think that data should always be written to the recovery folder every five minutes and persist there until it is overwritten by 'x' number of successive autosaves. (Autosave 1, 2 ,3 ,4 ,5, 1, 2, 3...) That way when an unforseen issue cripples the program loop to the point that whatever "write recovery data if crash = 1" subroutine never scans (because the entire program scan has stopped) you can still manually recover by double-clicking on the most recent autosave. Incidentally this is the same scheme that some video games use with great success.
 
Last edited:
Well, it didn't generate recovery data when it crashed for me. ;)

Seems kind of strange that such data would only be generated when the software detects a problem. You would think that data should always be written to the recovery folder every five minutes and persist there until it is overwritten by 'x' number of successive autosaves. ...........

But that IS exactly what happens, aside from not keeping older autosaves. After X minutes, it is autosaved. if the program dumps without saving, it is still there.

Perhaps the downfall of it is that it seems to be erased when a manual save is done. What happens then if the save fails? I have not been able to try that situation, so I do not know.

Was that what happened for you?

If not, you should check the autosave interval. Maybe you did not get to that, or the autosave itself crashed?
 
But that IS exactly what happens, aside from not keeping older autosaves. After X minutes, it is autosaved. if the program dumps without saving, it is still there.

Perhaps the downfall of it is that it seems to be erased when a manual save is done. What happens then if the save fails? I have not been able to try that situation, so I do not know.

Was that what happened for you?

If not, you should check the autosave interval. Maybe you did not get to that, or the autosave itself crashed?
I'm currently encountering an error upon saving where in the end all I can do is either Save As, or end the Alibre Task in Task manager and rebuild from Auto-Recovery upon restarting Alibre.
The last time this error occurred, I exited Alibre like you normally would and then upon restarting Alibre, all log files were erased.
So there is no manual save required to erase the recovery files, a regular shutdown seems to do that as well. Shame because I've lost some progress this way.

Thought I'd let you know.
 
Back
Top