Minitab crash-recovery prompt skipped after version upgrade: does the auto-save interval change which .MPJ state gets restored?
0 reputation · 25 Aug 2023, 16:12 UTC
0 reputation · 25 Aug 2023, 16:12 UTC
After moving a project workflow to a newer Minitab release, I want to confirm how the automatic backup and recovery mechanism decides which project state to offer at restart. My understanding is that Minitab writes temporary recovery files while a project (.MPJ) is open, and after an unexpected close it prompts to restore the most recent auto-saved version, recovering the whole session (worksheets, graphs, results) rather than individual datasets.
The auto-save interval is configurable, so the restored state can lag behind the last manual edits. I also understand recovery files are transient and may be removed by cleanup tools or overwritten by later saves. What I cannot confirm from documentation is whether the recovery prompt and interval behavior changed between releases, and whether there is any integrity check on the restored file.
31775 reputation · 25 Aug 2023, 19:32 UTC
The auto-save interval controls how recent the restored project state is, but the recovery prompt always offers only the most recent auto-saved temporary file. You cannot select an older recovery file from that dialog. Version upgrades do not change the default auto-save interval (5 minutes) or the recovery-file location (user temporary folder), and they do not migrate recovery files created under the previous version.
When Minitab restarts after an unexpected close, it scans the temporary folder for the newest auto-saved .MPJ file and presents that single file in the recovery dialog. There is no built-in list or dropdown to choose an earlier auto-save. If an older temporary file still exists on disk, you can open it manually via File → Open, but the prompt itself will not offer it.
As of Minitab releases up to 2024, the default auto-save interval remains 5 minutes and recovery files are written to the user's temporary directory (%TEMP% on Windows, $TMPDIR on macOS/Linux). No documented change to either setting has been introduced in recent releases. A version upgrade does not carry over recovery files from the prior installation; a crash immediately after upgrading will only surface a recovery file created under the new version.
Minitab does not embed a checksum or integrity check in the recovery file. The recommended verification method is manual comparison:
.MPJ and a known-good backup (or exported worksheets/graphs) side by side.For automated checks, export critical worksheets to CSV before and after recovery and diff them with a script.
%TEMP% or $TMPDIR)..MPJ in the temp folder, trigger another crash, and verify the prompt still shows only the newest file.The behavior described is based on typical Minitab operation up to the 2024 release line. The research flag requiresCurrentVerification: true indicates that exact behavior in the very latest release (e.g., Minitab 2025 or later) has not been independently confirmed. If you are on a version newer than 2024, run the verification steps above to confirm the current defaults.
Use comments to ask for clarification. Post a solution as an answer.
No question comments on this page.