3.93.1 was the last stable release of n8n (fixed in 3.97.0)

[umnz]

Update: This has been fixed by the n8n team, and Cloudron release 3.97.0 uses the updated image. Things seem ok so far. I recommend turning automatic updates off for n8n as they seem to be moving fast and breaking things.

====

Has anyone else noticed that all releases of n8n on Cloudron after 3.93.1 are pinging resources and seeing frequent timeouts? One of the updates stopped you from being able to login at all because the port was mapped incorrectly.

Any n8n users here that use the Outlook or Microsoft nodes notice an increase in failed executions or timeouts?

I'm not sure if it is the Cloudron build but these timeouts are hurting a lot of processes and web hooks.

Is there a way to downgrade without restoring a backup?

[umnz]

https://community.n8n.io/t/performance-problems-with-the-1-105-x-and-1-106-0-releases/161353/19

[umnz]

https://community.n8n.io/t/drastic-performance-drop-after-updating-to-1-105-2-large-workflow-execution-now-takes-60-seconds-instead-of-0-3/162566

[umnz]

Confirming that there is a huge issue with n8n and I would encourage you all to check the status of your instances and resources as the failures are relatively silent if you do not have any type of error notifications built into your workflows. @girish

[james]

Hello @umnz
Thanks for reporting this.

[umnz]

No worries. I'd be screwed if it weren't for Cloudron's solid backup/update management. I've turned off Automatic Updates for n8n as a result of this - I recommend other Cloudron users do the same.

[umnz]

Just an update for those who were affected and/or had workflows with advanced expressions - n8n have rolled back some changes and this release https://github.com/n8n-io/n8n/compare/n8n@1.107.1...n8n@1.107.2 which might have fixed the issue. Will have to wait and see.

[firmansi]

@umnz still pre release?

[umnz]

Yeah it's still pre-release unfortunately. So I can't update/test it yet.

[umnz]

@firmansi latest version was pushed to Cloudron