n8n 2.16.1 has wait node bug

[DualOSWinWiz]

@Package-Updates please do not update yet as 2.16.1 has a bug as wait node does not work

upstream issue was already created by someone https://github.com/n8n-io/n8n/issues/28632

[umnz]

@DualOSWinWiz said:

@Package-Updates please do not update yet as 2.16.1 has a bug as wait node does not work

upstream issue was already created by someone https://github.com/n8n-io/n8n/issues/28632

I don't think it has been fixed in 2.16.2 either. Not to mention there is a Websocket Connection issue. Pretty frustrating given there is a security release going out tomorrow and these are two major defects.

[girish]

@umnz oof, just saw this. Unfortunately, the updates are already. In the future please make separate threads. The package updates thread and that username is a bot and nobody is watching it.

[girish]

Maybe @james has better idea on how we can tackle this in the future. Should we make @package-updates some group instead of the automated user it is now?

[DualOSWinWiz]

@umnz you are rite i had to revert my 6 n8n instances on n8n 2.15.1 version..... at least i have backups and i disabled the auto updates for the time being

[DualOSWinWiz]

Make Wait node fully durable by removing in-memory execution path (#28574 ) (a4bdc80 )

I think current release will solve that i will try to update in non production hours and let you guys know

[DualOSWinWiz]

https://forum.cloudron.io/post/123862

[4.19.1]

Update n8n to 2.17.5
Full Changelog
core: Enforce credential access checks in dynamic node parameter requests (#28861 ) (9aadc28 )
Alibaba Cloud Chat Model Node: Add credential-level url field for AI gateway compatibility (#28746 ) (60b61ef )
Make Wait node fully durable by removing in-memory execution path (#28574 ) (a4bdc80 )

i can confirm that the above version has fixed the wait node issue

[DualOSWinWiz]

@james this is resolved

[umnz]

@dualoswinwiz are you sure? 2.17.5 was good - however on Friday last week I updated to 2.17.7 and it looked like a similar bug crept in again where things are not waiting or duplicate requests are being fired. Didn't have time to establish the root cause, so I reverted to 2.17.5 and things are "back to normal". I'm getting real tired of these releases from n8n. Now I'm spending 15-20 minutes reviewing the Issues board 2-3 days after each release just to see if it'll be safe to upgrade a version.

[umnz]

Also, I don't think I can trust their release logs anymore either. "Fix for Project Settings" and "Fix for Gemini" across two releases yet none of my Workflows use Gemini and a UI fix shouldn't impact my workflows - yet somehow, there are changes beyond what is being reported in the change log that are breaking things. Trust level is diminishing with these guys.