When workflow is scheduled we can't trigger it manually with latest 1.23.3 update

Describe the problem/error/question

With latest update the workflows that are scheduled cannot be manually triggered, only with manual trigger node next node is getting processed but with scheduler next node is not getting triggered

What is the error message (if any)?

No error message, it stops from next node on manually executing the scheduled workflow

Please share your workflow

Share the output returned by the last node

Information on your n8n setup

  • **n8n version:1.23.3
  • **Database (default: SQLite):postgres
  • **n8n EXECUTIONS_PROCESS setting (default: own, main): own
  • **Running n8n via (Docker, npm, n8n cloud, desktop app): AKS
  • **Operating system:Linux

None of the scheduled workflows are running, please check

Are they not running at all or only at different times? What you could try is to set the Schedule node to run every 30 seconds, wait till it got triggered and then look what time this nodes outputs. It is like that very easy to see if your time and the time n8n uses is identical and so if n8n is configured correctly.

All these scheduled workflows were running fine before I upgrade to 1.23.3 yesterday. after updation I don’t see any of the workflows scheduled are running.
We are running in a pod, where the logs shows error as
| error | TypeError: moment_1.default.tz is not a function “{ file: ‘LoggerProxy.js’, function: ‘exports.error’ }”

Tried updating the scheduler to run every 30 sec, workflow not started, and when checking the error in logs below recorded every 30 seconds,
2024-01-03T09:53:38.125Z | error | TypeError: moment_1.default.tz is not a function “{ file: ‘LoggerProxy.js’, function: ‘exports.error’ }”
2024-01-03T09:54:08.125Z | error | TypeError: moment_1.default.tz is not a function “{ file: ‘LoggerProxy.js’, function: ‘exports.error’ }”
2024-01-03T09:54:38.126Z | error | TypeError: moment_1.default.tz is not a function “{ file: ‘LoggerProxy.js’, function: ‘exports.error’ }”

This was fixed in fix(Schedule Trigger Node): Use the correct `moment` import by netroy · Pull Request #8185 · n8n-io/n8n · GitHub, and will be included in the next release.
Until then, we suggest that you downgrade to the latest stable release using the latest tag from docker hub.

Downgrading to 1.23.0 resolved the issue

2 Likes

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