Help for owners
I updated n8n and now my workflows are failing
Short answer
n8n tells you to read the release notes for every version between yours and the target, because updates can contain breaking changes. Changing the image tag back does not undo database migrations, so a rollback means either reverting migrations or restoring a backup taken before the update. Do not experiment on the live instance.
Does this sound like your situation?
- Workflows that ran fine for months now fail.
- A node I used is gone, or shows as unknown.
- A Code node cannot read a setting it used before.
- Webhooks or schedules stopped after the update.
- I put the old version back and n8n will not start.
Why does this happen?
Updates can contain breaking changes
n8n's update guide says to read the release notes of every version between your current one and the target, including the target, and to look for breaking changes. A jump over many versions stacks them up.
Confirmed by docs.n8n.io
Major versions change behaviour and security defaults
n8n's breaking-changes page for 2.0 lists, among others, a removed Start node, Publish and Unpublish replacing Activate and Deactivate, Code node access to environment variables blocked by default, task runners enabled by default, some nodes disabled by default, and support dropped for MySQL and MariaDB.
Confirmed by docs.n8n.io
Moving back does not undo the database
n8n states that each process runs pending migrations when it starts, and that changing the image tag back does not undo migrations. Some migrations cannot be reverted cleanly.
Confirmed by docs.n8n.io
Mixed versions and the latest tag
The docs recommend pinning a specific image tag instead of latest, and running the same version on all main processes, workers and webhook processors. A container that pulled a new version by itself can change things without anyone choosing to update.
Confirmed by docs.n8n.io
What can I do about it today?
- Stop changing thingsEvery restart, tag change or downgrade attempt can change the database further. Pause and write down what has been tried.
- Record the version before and afterWhich version ran before, which one runs now, and the exact time of the update.
- Find the backup taken before the updateAsk your host or developer whether a database copy and the encryption key were saved just before. This is your safe route back.
- List the workflows that matter mostOrder them by business impact so the important ones are checked first. Run the urgent ones by hand if you must, with care.
- Send your developer the error messagesCopy the node name and error text from the failing executions.
When should I bring someone in?
- n8n does not start after you moved back to the older version.
- No backup from before the update exists.
- Workflows handling orders, invoices or leads are failing.
How do I handle it?
- Secure a copy firstBefore any change I take a copy of the database, the data folder and the encryption key, so the current state can always be recovered.
- Read the release notes between the two versionsI list every breaking change that touches nodes, settings and features your workflows use.
- Fix forward on a copyWhere it is practical, I restore the copy on a spare machine, apply the fixes there and test the important workflows.
- Roll back only the documented wayIf a rollback is better, I follow n8n's two routes: reverting migrations one at a time, or restoring the pre-update database, accepting what the restore discards.
- Pin the version and test updates in futureThe image tag is pinned and updates go through a copy first.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Can I just reinstall the old version?
Changing the tag back does not undo migrations, according to n8n. A restore of the earlier database, or reverting migrations, is the documented route.
How often should I update?
n8n suggests updating regularly, ideally at least monthly, so you never jump many versions at once.
Will I lose recent executions if I restore a backup?
Yes. n8n notes that restoring the pre-update backup discards changes made after the backup was taken.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.