Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Schedule triggers not working (fix shipped in n8n 1.23 release) #55

Closed
LatitudesMaster opened this issue Mar 18, 2024 · 1 comment
Closed

Comments

@LatitudesMaster
Copy link

Hello,

First, a big thank you to all contributors to the n8n yunohost app, it's a pleasure to install it as easily 😍
Especially for our structure which don't have a full time dedicated tech team !

Describe the bug

Schedule trigger based workflows are not launching anymore.
That's an identified n8n bug, apparently fixed by this : n8n-io/n8n#8185

But this makes the 1.29 bump a fix to the issue for yunohost self-hosted n8n users !

This issue is here to share this info, and maybe get some advice if anyone fixed it another way in between !

Context

Hardware: VPS bought online
YunoHost version: 11.2.10.1
I have access to my server : Through SSH & through the webadmin
Are you in a special context or did you perform some particular tweaking on your YunoHost instance ? : no
If your request is related to an app, specify its name and version: n8n 1.9.3~ynh1 (latest)

Steps to reproduce

  • Create a workflow with a schedule trigger
  • Correctly select a timezone (n8n docs point out that it's mandatory)
  • Save and activate the WF
  • Wait forever :)

Expected behavior

Normal start for workflows.

Logs

In n8n service logs, I get this error (which led me to the n8n fix quoted above)

Mar 18 17:01:58 n8n[2467897]: TypeError: moment_1.default.tz is not a function
@LatitudesMaster
Copy link
Author

Hello 👋
The version bump solved this issue, thanks for merging the PR !
Nicolas

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant