Hi everyone,
I’m running n8n locally via Docker and my Schedule Trigger workflow is not firing automatically.
Setup:
- Docker with
restart: always
- n8n version
2.20.7-exp.0
- Simple workflow: Schedule Trigger → Telegram message
Problem:
The workflow runs fine when I click “Execute Workflow” manually, but never fires automatically at the scheduled time. The workflow shows as “Published” in the UI.
Logs show:
Processed 1 draft workflows, 0 published workflows.
Activated workflow "..."
Deregistered all crons for workflow
The workflow is activated but crons are immediately deregistered. I suspect this is a bug in the experimental version 2.20.7-exp.0.
Has anyone experienced this? Any help appreciated!
Describe the problem/error/question
What is the error message (if any)?
Please share your workflow
(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)
Share the output returned by the last node
Information on your n8n setup
- n8n version:
- Database (default: SQLite):
- n8n EXECUTIONS_PROCESS setting (default: own, main):
- Running n8n via (Docker, npm, n8n cloud, desktop app):
- Operating system:
Is your timezone settings set correctly?
Also, can you downgrade your n8n version?
welcome to the community @dagama123 !
First of all, follow kjooleng’s steps. go to the current version
From what I saw in your log, it seems that n8n is not recognizing the workflow as draft during initialization. this message here indicates that “Processed 1 draft workflows, 0 published workflows”.
Have you tried exiting the image, republishing, reactivating the workflow and restarting the container?
This is a known bug, it does not affect the functionality at all
I don’t know .I simple wrote me time zone in the docker .For example too.Thanks for the advice, I’ll check.
yes I try republishing workflow three times and reactivating workflow restarting docker too didn’t help.because I looked up information on GPT before publishing Because before posting, I looked up information on GPT, and it suggested checking the latest logs for N8N. Then I tried that for two days on N8N version 2.14.2. After that, I updated to 2.20.7-exp.0, but that didn’t change anything. The problem is that when I run the process manually, everything works, but not when it runs automatically. But thanks for the advice.
@dagama123
First of all, update to version 2.20.8, the stable version.
I would check if the container is pointing to the correct database/volume and if the workflow really has active=true. As a quick test, I would create a new workflow with just Schedule Trigger + Telegram/NoOp, restart the container and validate if it appears as published in the logs.
