If I restart the docker instance, are the workflows currently in "waiting" status resume after that?

Questions
,
1

Describe the problem/error/question

In my digital ocean instance of n8n, I made some changes in the environment variables, so for it to save, I have to do docker compose down followed by up -d. Will executions currently in “waiting” status survive and resume properly, or do they get lost or cancelled?

Information on your n8n setup

  • n8n version: 1.122.5
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • Operating system:
2

Hey @alejandro12850 !

Yea, as long as your DigitalOcean droplet is configured with persistent Docker volumes for your database and n8n data, your waiting executions will survive the docker compose down and resume once the instance is back up.

Cheers!

3

ohhh i see, thank you! im just a bit worried because i asked AI and it says that in many cases users report that executions are not deleted but never “wake up”, instead remaining in a waiting state forever. But probably that happened in older versions, and i asked another AI and also says its ok