Cloudpeakify · Free lab evidence sample
n8n recovery drill: observed results
Reference: n8n 2.39.9 / Node 24.21.0 / SQLite / Linux
Checked: 2026-09-21
This readable sample summarizes actual lab observations using synthetic workflows and dummy credentials. It is an example of a recovery record, not a report about your installation.
| Check | What we did | Observed result |
|---|---|---|
| Restored data | Copied the complete data folder after a clean stop, then started a separate same-version instance. | Backup and restored-copy hashes matched before startup; the restored instance became ready. |
| Workflow comparison | Exported workflows from the actual source and restored n8n installations. | Checker exit 0: semantic_match. Metadata warnings remained; recovery_verified stayed false. |
| Restored execution | Executed the harmless two-node workflow against a local HTTP endpoint. | n8n CLI exit 0 for both the source and the restored workflow. |
| Credential usability | Authenticated from the restored workflow with the copied encrypted dummy credential. | The local endpoint accepted the restored credential; its value was not included in the report. |
| Deliberate parameter change | Edited the HTTP timeout in a local copy of the real restored export, from 5000 to 4999. | Checker exit 1: semantic_difference in the nodes section. This edited file was not a fresh n8n export. |
| Missing original key | Removed the original key configuration from another scratch copy, then exported and executed its workflow. | Workflow comparison still matched. Actual execution failed to decrypt the credential and made no new HTTP request. |
How to interpret this record
The same-version restore, credential check and execution check are separate from the offline workflow comparison. A deliberately changed parameter or missing original key is expected to fail its relevant check. The checker reports recovery_verified: false; a matching export does not prove complete recovery.
Tested 2026-09-21: n8n 2.39.9, Node.js 24.21.0, Linux, SQLite and synthetic data. One inactive two-node workflow, one encrypted dummy credential and a local HTTP endpoint; a stopped data-folder copy into a separate same-version instance. PostgreSQL, Docker volume recovery, queue mode, external providers and arbitrary n8n upgrades are outside this test.
Existing kit archive SHA-256: c1be6fe7d95fea272839a9cf374a9df84bb761e9054adce93ece8d86052611d3. The published lab checks the unchanged customer tool. This sample contains no production secrets or customer information.