Advice on Upgrading 50+ versions

Hi!

We’ve been using N8N for about 2-3 years, though are currently about a year behind in updates. We’re at 0.221.2, though are needing some troubleshooting of different nodes and authorisations, which I understand would only really make sense helping with once we have udpated.

I can see since our most recent update, there have been 51 updates including 2 security updates (0.233.1, 1.44.1) and 1 breaking update (1.0.5)

I was hoping to get any advice on the best way to approach getting up to date? We’ve got around 200+ flows that ideally we’d want to minimise breakage obviously, though minimising the amount we would need to go and fix all at once is the preferred outcome.

Thanks!


Information on your n8n setup

  • 0.221.2
  • Self hosted on AWS

It looks like your topic is missing some important information. Could you provide the following if applicable.

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

Hey @LBAdam,

Other than “carefully” I think I would make a backup of the workflows and credentials using the CLI then I would do one of 2 things…

  1. Go for it and see what happens, If it doesn’t work restore from backup.
  2. Set up a new server and install the latest release then import the credentials and workflows and test them so you can enable on one disable on the other

There are some things to think about with the upgrade as well, It may take a long time if you have not been keeping on top of the execution data can you share the env options you have set?

Personally I would go with the second option which gives you a chance to explore the new features and test the workflows as you get time.

2 Likes

Thanks for this reply, Jon. It is quite helpful.

Unfortunately, what it helps me to understand is the size of the task we have ahead of us is pretty large.

We have a medium term goal of updating the instance, as its just the correct thing to do, though the short term reason we were looking at doing this is to get troubleshooting help with the Authentication within the Zoho CRM node.

Is there any chance we could get some help on that Node, regardless of our current instance? Or would help only be able to be achieved after getting up to date?

Hey @LBAdam,

What is the issue with the Zoho CRM node?

Hey @jon

It was outlined here a few months ago, Predefined Zoho Authorizations Not Working For HTTP Client and whilst this is still true - the standard authentication process with Zoho CRM node also fails repeatedly now when setting up a new credential. When speaking to Zoho, they are highlighting that the process is needing to send through another token that comes back in the URL, though it is not doing so.

I am not sure if the credential creation issue is resolved in the more recent versions of N8N, but I am hoping that this gives enough insight to make it understood what I am talking about. I can forward the email from the Zoho Support team that highlights the issue more eloquently if there an address I can send to?

Thanks!

1 Like