Hi Support Team,
I’m running self-hosted n8n on Hostinger. I want to review older workflow execution history (including Dec 2025).
Can you please confirm:
Is my n8n database stored on persistent storage (not wiped during restarts/deployments)?
Was execution history being saved in my n8n setup (successful + failed executions), or was it disabled?
Do I have any auto-cleanup/pruning enabled (for example execution data pruning / max age retention)? If yes, what retention period?
Do you have any server backups / database backups that would still contain execution history from Dec 2025? If yes, can it be restored or exported?
If you need details, tell me what you need (domain/instance, container setup, database location).
Thanks!
Thanks for reaching out.
In a self-hosted n8n setup, all execution data is stored only in the database you configured on your own server, and n8n (as a company) does not keep any external copies or backups of that data.
By default, n8n saves all execution histories, but it also enables automatic cleanup. Unless you changed the default settings, executions older than about 14 days or beyond the maximum stored count are automatically pruned. This means executions from December 2025 would normally have been deleted by design, not due to an error.
The only way to recover data that old would be from your own server or hosting provider backups. If Hostinger has a database or volume backup from that time, you could restore it to a separate instance and export the old executions from there. Without such a backup, it unfortunately isn’t possible to restore execution history from that period.
To help further, could you share how n8n is deployed (e.g. Docker or direct install), which database you use (SQLite or Postgres), and your execution pruning settings (like EXECUTIONS_DATA_PRUNE and EXECUTIONS_DATA_MAX_AGE)?
With that we can confirm whether the old executions were automatically deleted and what kind of backups you would need to check with your host.
[Supported DBs]
[Privacy self-hosted]
[v1.0 migration; Executions env vars]
[v1.0 migration; Enable pruning]
Executions env vars]