N8n Workflow Still Running Even When Set to Inactive

[muhfalihr]

Hello everyone,

I’m encountering an issue where a workflow in n8n continues to run even after I’ve set it to inactive.

Here’s the setup:

• The workflow uses a Kafka trigger.
• It parses the incoming data and sends the parsed result to Telegram.
• However, the executions that are still running appear to be from a different version of the workflow than the current one.

Environment details:

• n8n version: 1.103.2
• Database: PostgreSQL
• Queue: Redis (Bull)

Has anyone experienced this before? Any advice on how to properly stop all executions or make sure no previous versions of the workflow are still being triggered?

Thanks in advance!

Information on your n8n setup

• n8n version: 1.103.2
• Database (default: SQLite): Postgresql
• n8n EXECUTIONS_PROCESS setting (default: own, main):
• Running n8n via (Docker, npm, n8n cloud, desktop app): Kubernetes
• Operating system: Debian

[King_Samuel_David]

Hey @muhfalihr

Yes this happends, am not 100 percent sure why, but coping the workflow into a new workflow normally fixes it, did you try this?

Samuel

[muhfalihr]

I’ll try that approach. It looks like the issue can be resolved by deleting the old workflow and running the duplicated version. However, this seems more like a workaround, and the bug could potentially become a persistent problem in the future.

[King_Samuel_David]

@muhfalihr Yeah am quite sure they have a bug ticket open as it’s been about for sometime now. But i’d have to check see on github, but I dont think I can see all issues raised Hopefully it’s fixed soon.

I just try avoid adding more than one trigger w schdule, and don’t edit the trigger to much as it causes this I find.

Samuel