File Recovery - What's the correct workflow?

File Recovery - What's the correct workflow?

l_wcrenshaw
Advocate Advocate
654 Views
6 Replies
Message 1 of 7

File Recovery - What's the correct workflow?

l_wcrenshaw
Advocate
Advocate

Long time F360 user, but not much forum poster.  I've been pretty deep into a project using F360 for the last 1.5 mos, and I've had my fair share of crashes.  My question is, when I restart the program and F360 displays the pop-up that says it's recovered a file, what is the correct process to get that model back into the versioning system in the project panel on the left of the screen?  If I use the recovered file for say "Whizbang (v20~recovered)", it's now really version 1 of that model with no way to roll back to, say, version 19.  I appreciate what's being done, but I'm trying to figure out a non-kludgey way to integrate the recovered model back into original model's timeline.  Thanks.

 

 

0 Likes
Accepted solutions (1)
655 Views
6 Replies
Replies (6)
Message 2 of 7

jeff_strater
Community Manager
Community Manager
Accepted solution

Good question, @l_wcrenshaw.  How this is supposed to work is:  When you open the recovery file, it does show the "recovered" name, but Fusion is aware of its link to the correct design in your project.  If you save this design, it should link back up to the correct design, and just add a new version to the history of that object.  If you close without saving, you are telling Fusion that you are not interested in this recovery file, similar to if you delete it from the recovery dialog.  I think the intention is that this visually distinguishes recoveries from "normal" designs in your session, just to make you aware of the fact that this is a recovery version.

 

Jeff

 


Jeff Strater
Engineering Director
0 Likes
Message 3 of 7

l_wcrenshaw
Advocate
Advocate

Thanks, Jeff.  Interesting.  That's how I assume it should work.  Maybe I did something wrong, but this happened to me a week ago and now I have version52 of the model and 2nd recovered model that's up to version26.  I just retired the old model and kept plugging along with the new one.  This just happened to me again which why I posted.  I'll try to be a little more cognizant the next time this happens to try and avoid whatever I did.

0 Likes
Message 4 of 7

jeff_strater
Community Manager
Community Manager

Interesting.  I think I have run into that situation before, so if you can remember the steps needed to get there, it'd be helpful.  I did just test the basic workflow, and it does work.  If you save, it should re-connect to it original design, and just add a new version.  But, I'm sure there are workflows where this can go south.  Like, for instance, if you crash again before saving, I'm not sure what happens.

 

Jeff

 


Jeff Strater
Engineering Director
0 Likes
Message 5 of 7

r.moss
Advocate
Advocate

I've just had a similar experience and I'm wishing I had read this thread before re-saving.

 

I was working on a design, let's call it "Basin", up to version 29.

 

I clicked "Save", then after about 10 seconds I closed Fusion.  It gave the usual message that it would close once files had finished uploading.

 

I came back half an hour later and re-opened Fusion.  It gave a message saying that a recovery file was available, so I opened it (I guess the network connection had been lost during saving).  The window title was then something like "Basin (recovery file) *".  [The old v.29 file was from about an hour earlier and I had made a lot of changes inthat time].

 

I didn't want the file name to be "Basin (recovery file)" so instead of "Save" I clicked on "Save as" and selected "Basin", thinking it would save it as a new version (v.30) of the original design.

Instead, it created a new file with the same name, starting at v.0.

 

My problem is that Basin v.29 was inserted as a component in a larger assembly.  I cannot switch that to Basin v.0 because it sees the new file as a separate design.  I have tried looking for the recovery file under AppData\...\CrashRecovery but it seems to have been deleted (and it's not in the Recycle Bin either, and "Open recovered documents" has no entries).

 

I could insert Basin v.0 as a new component in the assembly, and get rid of the v.29 component, but I think if I do that any drawings of the assembly will get very confused about which objects are visible, dimension relations etc.  Fortunately I haven't finished the drawings yet, but in principle this brief moment of carelessness could have cost me many hours' work.

 

It seems a bit of a fragile system.  Is there any way of getting the recovery file back so I can try again?  Or redefining v.0 as v.30 of the old file?

 

 

 

0 Likes
Message 6 of 7

jeff_strater
Community Manager
Community Manager

yes, I think.  I tried this long ago, and it worked, hope it still does.  Open the recovery file that you did Save As on, and export an F3D (hopefully it is a single F3D).  You can then use "import new version" from the data panel, and choose your exported F3D.  This will create a new version (V30) of the design, and references to it should show correct out of date behavior, and update correctly

Screen Shot 2020-07-23 at 11.10.31 AM.png


Jeff Strater
Engineering Director
0 Likes
Message 7 of 7

r.moss
Advocate
Advocate

Thanks very much - seems to have worked.

 

Roger

0 Likes