Please Add an Option to Disable Autosave

Feature Requests
1

The idea is:

Hello n8n team and community,
I am writing to strongly echo the requests made in this previous thread: Disable Autosave
As developers, having the freedom to test, experiment, and break workflows without committing those changes is crucial. With the forced autosave feature in v2.x, every exploratory edit is permanently recorded, which clutters the version history and makes it terrifying to experiment on complex, production-critical workflows.
Because of this single issue, I am still forced to use n8n version 1.x. I have been waiting for months for a native UI toggle or at least an official environment variable to disable autosave, but nothing has been officially released yet.

My use case:

I think it would be beneficial to add this because:

Please prioritize adding a simple toggle in the UI (or an environment variable like N8N_WORKFLOWS_AUTOSAVE_DISABLED) that allows us to turn off autosave and return to manual saving.
Are there any official updates or ETAs on when we might see a solution for this? We really want to upgrade to v2.x but this is a hard blocker for our workflow.

Any resources to support this?

Are you willing to work on this?

2

I fully support this petition. Currently, self-hosted instances only retain one day of history unless you have a subscription. If disabling the auto-recording feature isn’t an option, I suggest extending the free history limit to at least a week or a month to make it more viable.

1 Like
3

+1 for this

There’s a PR open by @uppinote20 for this, please merge this ASAP:

1 Like