That usually points to a persistence or environment issue, not n8n randomly deleting a workflow. In self-hosted setups, workflows are stored in the database, so missing persistence, a recreated container, or a different instance/database can make them appear to “disappear.”
For Docker, I’d first check whether the correct volume is still mounted and whether the instance is still pointing to the same database; if more than one instance is running, I’d also verify they all share the same backend state.
It’s also worth checking whether the workflow was moved to trash, deleted, or whether this was a trial or temporary environment, since retained data can depend on how that instance was set up.
If you share the install method, database, and whether this happened after a restart or redeploy, that should narrow it down quickly.
Hi @David_Muwanguzi Welcome!
Please consider giving us more information related to your environment, problem, n8n instance so that we can actually help you.