Error in n8n container logs (not able to resume workflow)

Describe the problem/error/question

I have a recurring error (once a munite) in n8n container logs.
Probably I deleted some initial workflow when playing with n8n.

What is the error message (if any)?

There was a problem starting the waiting execution with id “58”: “Only saved workflows can be resumed.”

Please share your workflow


Share the output returned by the last node


Information on your n8n setup

  • n8n version: 0.222.2
  • Database (default: SQLite): Postgres
  • n8n EXECUTIONS_PROCESS setting (default: own, main): no such setting (probably “own”)
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker on Ubuntu (WSL2)
  • Operating system: Windows 11 + Docker Desktop

Hi there @vkarbovnichy - welcome to the community :tada:

Unfortunately, this is a deleted workflow that also somehow is referenced in the executions. I tried playing around with this and each time my workflow executions were removed immediately upon deleting the workflow from both the UI and the database. This happened both in Postgres and in SQLite, so I’m not too sure why this happened to you.

What I’d suggest is deleting these hung up executions from the execution_entity table to stop the error from happening.

Let me know if that helps!

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.