my work is gone!
Answers
-
No, everything from #58 forward is gone! At one point I had the program open in two places at once. Could this have caused my work to not be saved...or saved somewhere in the cloud?
0 -
I fear you could have been indexing on a cached screen and weren't really logged in and that is why it didn't save. Just a theory though.
1 -
it could also be that the last instance of your sessions to be closed out “had the last say” and that was saved when you exited it. And maybe that was where you had made less progress thus overwriting your advancement. I’ve had two sessions open for various experiments. It’s always a bit risky to do it because you absolutely need to keep track of which one is your working/primary session. AND make sure to close the secondary session first and then the primary one, so that the primary session has the “last say.”
Use of Share Batch: You still need to do this tracking (maybe use a post-it), but you might avoid your exact issue by opening the non-primary/ secondary session as a Shared Batch. Then you know that your work there cannot be saved. Only your work in the primary session can be saved. But a Corollary and caveat is: always and only do your real work in the primary session.
You definitely need to avoid doing work in the SB session that you want to save, because it will not be saved. And even when using the SB approach it can get confusing because I’ve found that if you refresh your SB session, it will be updated to reflect the current state of the primary session. This can be an asset when using SB to train a new Indexer, but confusing in your setting. So use a sure-fire way of distinguishing the two sessions.
2