GN4 has built-in session check and auto-recovery from crash.

When a GN4 application starts, it first checks if the previous session (if any) ended in a regular way. If this wasn't the case, and the previous session ended with a crash, it will prompt you to reload and recover all items you were working on at the crash time. These includes: articles, pages, layers, articles libraries etc.

The recovery is optional: upon restart after a crash the user is prompted to reload all the elements or not.

We strongly recommend you to accept it, so the items do not remain locked.  Then - if you want to work on some other item - close all document windows, and load what you want.

How it works?

The crash recovery system works as follows: every time GN4 opens or locks an element the operation is recorded in a log entry in the database, related to the user. Every time an element is closed or unlocked, the related entry is deleted from the log entry. When the program exits normally, the entire log entry is deleted from disk.

When the program starts, it checks if the log entry exist and if it was created by the same user. If this holds true, it means that there was a crash, and that the entry itself contains the list of the elements to reload.

About saving content

When the software crashes, all unsaved changes are lost. See Automatic save for the instructions how to enable and configure the auto-save.

About a local save of text content

When the local auto-save is enabled in Ted4, a copy of the content of all the modified texts is written in the local disk, avoiding accesses to the database, and the name of these local files is recorded in the log entry. When doing a crash-recovery, GN4 automatically reloads the content of the texts from these files.

The local save doesn't exist for Fred4 pages.