Hello i am using the version of n8n Version 1.103.2
I had a workflow configured for a client, the workflow has over 100 nodes, and suddenly when i came back from lunch the workflow was deactivated and most of the nodes were not set up properly, like a deconfiguration.
No one on my team made any changes, and i was pretty worried when i first saw that.
¿Has anyone had the same issue ever ?
I mean this has never happened before and i am not sure what has happend.
Hi @ALEJANDRO_BERROJO
This isn’t a known or common issue in n8n. The scenario you described—a workflow suddenly deactivating and having its nodes “deconfigured” without any user intervention—is highly unusual.
Did you check the Logs? Review your n8n instance’s logs for any errors or unexpected restarts around the time the workflow was deactivated. This is the most direct way to find out what happened.
Also remember to Backup Your Workflows: Regularly back up your workflows by exporting them as JSON files. This will serve as a safeguard against any accidental changes or data loss.
Ran into the issue for the first time yesterday.
When changing the name of the workflow and saving it most configurations were gone. Also had a webhook be disabled in the background for this flow, although it still said the flow was active.
v. 1.99.1
No idea what is happening there, but a weird issue indeed. I am not spending time on debugging though, as I will first update the instance when I get the chance.
This happened to me last night for the first time ever. I’m using version 1.106.2.
Same here. Workflow getting disabled out of the blue (and couldn’t see any logs abount it). Running on self-hosted 1.108.2 version.
Ok, guys, maybe I got the point.
In my case:
The Chrome extension “Tab Suspender” was deactivating my workflows for no reason after n8n workflows page returned from a suspended tab…
So, check your Chrome extensions…
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.