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.

Sign up for GitHub

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

Jump to bottom

1.22.3 scheduled job not running #8184

Closed
dynek opened this issue Dec 29, 2023 · 1 comment · Fixed by #8185
Closed

1.22.3 scheduled job not running #8184

dynek opened this issue Dec 29, 2023 · 1 comment · Fixed by #8185

Comments

@dynek
Copy link

dynek commented Dec 29, 2023

Describe the bug
Scheduled job are not running anymore, and when executed manually, they freeze (spinning wheel forever).

To Reproduce
Try to run a schedule node

  1. Right click schedule node
  2. Click on 'execute node'
  3. Spinning wheel forever and log say "TypeError: moment_1.default.tz is not a function"

Expected behavior
Schedule node should run

Environment (please complete the following information):

  • OS: Linux (Docker Container from Docker hub)
  • n8n Version: 1.22.3
  • Node.js Version: v18.18.2 (Docker Container from Docker hub)
  • Database system: SQLite
  • Operation mode: left untouched

Additional context
Reverted to 1.22.1 and everything works again.
netroy added a commit that referenced this issue Dec 29, 2023
@netroy
fix(Schedule Trigger Node): Use the correct moment import
8fcf97a 
This fixes #8184
@netroy netroy mentioned this issue Dec 29, 2023
Merged
2 tasks
netroy added a commit that referenced this issue Jan 2, 2024
@netroy
fix(Schedule Trigger Node): Use the correct moment import (#8185)
17a4e2e 
Any node that uses `moment.tz` should import from `moment-timezone`
instead of `moment`.

This fixes #8184
ivov pushed a commit that referenced this issue Jan 3, 2024
@netroy @ivov
fix(Schedule Trigger Node): Use the correct moment import (#8185)
f8307dc 
Any node that uses `moment.tz` should import from `moment-timezone`
instead of `moment`.

This fixes #8184
@github-actions github-actions bot mentioned this issue Jan 3, 2024
Merged
ivov added a commit that referenced this issue Jan 3, 2024
@github-actions @ivov
🚀 Release 1.22.4 (#8204)
6db03f0 
##
[1.22.4](https://github.com/n8n-io/n8n/compare/n8n@1.22.3...n8n@1.22.4)
(2024-01-03)


### Bug Fixes

* **Schedule Trigger Node:** Use the correct `moment` import
([#8185](#8185))
([f8307dc](f8307dc)),
closes [#8184](#8184)

Co-authored-by: ivov <ivov@users.noreply.github.com>
@github-actions github-actions bot mentioned this issue Jan 3, 2024
Merged
ybom77 pushed a commit to ybom77/yiyan8n that referenced this issue Jan 3, 2024
@netroy @ybom77
fix(Schedule Trigger Node): Use the correct moment import (n8n-io#8185
a98349f 
)

Any node that uses `moment.tz` should import from `moment-timezone`
instead of `moment`.

This fixes n8n-io#8184
@dynek
Copy link
Author

dynek commented Jan 4, 2024

Moved to 1.23.0 and it's working again, thank you 👍

@rorpage rorpage mentioned this issue Jan 15, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix(Schedule Trigger Node): Use the correct moment import n8n-io/n8n
1 participant
@dynek