Files usually break while they are being saved. And on a shop floor, power does not go out at a moment anyone chose.
A save that is interrupted leaves half a file
If power drops or the program is force-closed while a file is being overwritten, what remains is neither the old content nor the new. That file either will not open or, worse, opens with the wrong values.
If it is a recipe file, that day’s production stops. If it is a settings file, a day goes into finding the cause. Even with a backup on hand, the first job is working out which copy is still intact.
A save is either finished or never started
AimFactoryCore handles every recipe and settings file with an atomic save. If the app is killed or power drops during a save, the file is always left in a complete state. A half-written state is never created in the first place.
The last good copy stays alongside, and a damaged file is rolled back
Every save keeps the previous good copy next to the file. If corruption is detected, the damaged file is quarantined and the last good copy is restored automatically.
It is not a sequence where the operator notices something wrong and then acts. The software checks first and rolls back.
Once a day, the latest 30
Once a day at startup, the full recipe set is compressed and archived. The latest 30 are kept, so you can go back to the state of a month ago.
It means there is material left to check when someone says “it worked fine until yesterday.” The restore procedure is in the Help manual under data backup and recovery.
Where this matters
- Plants where voltage sags or power cuts are not rare
- Multi-model lines with dozens of recipes accumulated
- Sites where no engineer stays on after the equipment is handed over
