Wait node does not triger after updating to [email protected]

Questions
1

:wave:t3: Hey everyone,

Yesterday, I took the leap and upgraded n8n from version 1.34.2 to 1.36.1. However, shortly after the upgrade, I encountered an issue with the Waiting node. It seemed to change the workflow status to “Waiting,” but unfortunately, the workflow never triggered after the designated waiting period. To troubleshoot, I reverted back to the older version, and the stalled workflows resumed functioning as expected. Interestingly, I found that they also worked fine with version 1.37.0.

P.S.: Just a quick note on my environment variables: the timezone is set to Europe/Vilnius via GENERIC_TIMEZONE.

Example workflow:

2

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:
3

Hi @Rugia

If I understand correctly it is already fixed in the new version then?
But very nice of you to report anyway as it might help some others that have the same issue or stop them from updating to this broken version if they are dependant on the wait node. :slight_smile:

5

Yes, it doesn’t seem to have been addressed in the upcoming (next ) version, but I felt it’s important to highlight that users might encounter issues with the Waiting node when using the latest version, 1.36.1 , especially if they pull their images using the ‘latest ’ tag

1 Like
6

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.