Is there an alternative trigger node to schedule trigger?

Questions
1

Describe the problem/error/question

I have just updated to version 1.56.2 from 1.55.3 but the issue is persistent. when trying to use the schedule node at first you struggle to save the workflow it keep giving the error Workflow could not be activated:There was a problem activating the workflow: “ERROR: You specified an invalid date.” but after some retries it may save and you expect it to run on scheduled times but I have only gotten 2 executions before it completely stopped triggering and nothing

What is the error message (if any)?

Workflow could not be activated:

There was a problem activating the workflow: “ERROR: You specified an invalid date.”

Please share your workflow

Share the output returned by the last node

Information on your n8n setup

  • **n8n version:1.56.2
  • Database (default: SQLite):
  • **n8n EXECUTIONS_PROCESS setting (default: own, main):own or default
  • **Running n8n via (Docker, npm, n8n cloud, desktop app):docker
  • **Operating system:linux
1 Like
2

Hi @Onlypfachi

I just updated my n8n to 1.56.2 to check this issue. I do not have the same issue, so might be something wrong that is specific to your instance. Do you have a timezone set?

3

yes @BramKn the timezone is set and is set to “Africa/Johannesburg”

4

If you look at the settings of the workflow, does it show the timezone properly as well?

If that is all good then I have no idea what it could be. Can you share your setup so someone smarter than me can have a look?

1 Like
5

@BramKn

version: "3"
services:
  pgsql:
    image: "postgis/postgis:15-3.3-alpine"
    environment:
      - POSTGRES_DB=n8n
      - POSTGRES_USER=postgres
      - POSTGRES_HOST_AUTH_METHOD=md5
      - POSTGRES_PASSWORD=<redacted>
    expose:
      - 5432
    networks:
      - proxy
    volumes:
      - /mnt/postgresql:/var/lib/postgresql/data
    healthcheck:
      test: ['CMD-SHELL', 'pg_isready -h localhost -U postgres -d n8n']
      interval: 5s
      timeout: 5s
      retries: 10

  n8n:
    container_name: "n8n"
    restart: always
    image: n8nio/n8n:1.56.2
    environment:
      - WEBHOOK_URL=<redacted>
      - DB_TYPE=postgresdb
      - DB_POSTGRESDB_HOST=pgsql
      - DB_POSTGRESDB_PORT=5432
      - DB_POSTGRESDB_DATABASE=n8n
      - DB_POSTGRESDB_USER=postgres
      - DB_POSTGRESDB_PASSWORD=<redacted>
      - EXECUTIONS_DATA_PRUNE=true
      - EXECUTIONS_DATA_MAX_AGE=336
      - NODE_OPTIONS=--max_old_space_size=8000
      - NODE_TLS_REJECT_UNAUTHORIZED=0
      - N8N_LOG_LEVEL=verbose
      - GENERIC_TIMEZONE="Africa/Johannesburg"
    expose:
      - 5678
    volumes:
      - /mnt/n8n:/home/node/.n8n
    networks:
      - proxy
      - services
    depends_on:
      - pgsql
      - redis

  redis:
    image: redis
    container_name: redis
    restart: always
    networks:
      - proxy

networks:
  proxy:
    external: true
  services:
    external: true
6

I have the same problem. It was fixed after updating my instance to V1.57.0.

1 Like
7

@anas what happened?

8

please do not just delete your post if it stopped working again. Now we have to guess why you deleted the post. :sweat_smile:

2 Likes
9

So Sorry @BramKn @Onlypfachi, guys. I thought my comment might affect your investigation it contain false info so deleted it; as a last result, the problem is not fixed with the latest updates.

For me, I was able to save the workflow, but it won’t run on the scheduled date.

I also figured out that if you add any other trigger with it (like a manual trigger), the workflow will be saved even with old versions.

To do a quick fix until it gets resolved, I added a Manual Trigger with a “Wait” node and a repeat loop. :laughing:

10

I have the same issue even after updating to 1.57.0

1 Like
11

@Onlypfachi Did you submit a bug issue for it? if not do it and we should comment there.

Issues · n8n-io/n8n · GitHub

12

@anas i have created the report here you can also add info there