Updating to latest version renders Cron/Schedule trigger unoperational

Questions
1

Describe the problem/error/question

After updating to latest version (v1.59.4) all cron triggers / schedule triggers are forced deactivated. Please note that i update around bi-weekly and the cron task worked for past few months for me since i started using n8n. My server setup did not change. Only change was updating to latest version.

What is the error message (if any)?

On activation i get

There was a problem activating the workflow: "Invalid cron expression"

for Custom(cron)
and

Workflow could not be activated:
There was a problem activating the workflow: "ERROR: You specified an invalid date."

for selection via the dialog Trigger Rules -> everyday etc.

Please share your workflow

Share the output returned by the last node

no output, can’t not run

Information on your n8n setup

# Debug info

## core

- n8nVersion: 1.59.4
- platform: docker (self-hosted)
- nodeJsVersion: 20.17.0
- database: sqlite
- executionMode: regular
- concurrency: -1
- license: community
- consumerId: unknown

## storage

- success: all
- error: all
- progress: false
- manual: true
- binaryMode: memory

## pruning

- enabled: true
- maxAge: 336 hours
- maxCount: 10000 executions

Generated at: 2024-09-25T09:26:14.183Z

running on linux 20.04 via docker compose, sqlite

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

I’ve seen a few reports of this, but so far not able to reproduce this. So far all I can tell is that this has something to do with timezone.

What’s your instance timezone set to?

4

in docker-compose.yml i have
- GENERIC_TIMEZONE="Europe/Berlin"
and in the workflow it does not matter what i set for timezone, it still wont allow me to activate the workflows…

5

Can you please try removing the quotes?

- GENERIC_TIMEZONE=Europe/Berlin
6

Thank you, that did it.
Did i miss these changes in the changelog?
I noticed also - N8N_LOG_LEVEL changed from verbose not being valid

n8n-1  | message: logs.level: must be one of the possible values: ["silent","error","warn","info","debug"]: value was "verbose"