Where Does Shuffle Store Workflows and History?
Where self hosted Shuffle keeps workflows in database on Linux servers. Full paths are listed below.
Last updated
Shuffle is SOAR automation with server storage. The database holds workflows, apps, and executions. Workers cache runs locally per job.
Same database means same playbooks. Exact paths vary by Docker versus binary installs. Keep backups on schedule. One missing table restores workflows without history. For moves, stop workers first to avoid split executions during copies. When in doubt, verify paths inside the app before trusting a remembered folder. Screenshots of settings help when support asks for reproduction steps later.
Where Shuffle SOAR stores this, by platform
/var/lib/shuffle (database, paths vary by install)
Playbooks live in the server database with execution history. Back up the database stopped. Match releases before restore. Workers cache locally.
Frequently asked questions
How do I migrate Shuffle to a new server?
Back up the Shuffle database with services stopped, then install the same release on the new server before restore. Workflows follow the database. Mixed releases can refuse old schemas, so match versions first. Keep API keys separate from shared copies.
Does Shuffle back up execution history?
Yes, in the server database per execution with results attached. The host holds a working copy plus worker cache. Views rebuild after restore. Export JSON workflows from settings for records, since the data directory alone is working state.
Notice an outdated path? Let us know.