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?