Help for owners
My n8n workflow works when I click it but does not run by itself
Short answer
In n8n a manual test and a scheduled run are different things. A schedule only runs for a published workflow, and a changed interval takes effect only after you unpublish and publish a new version. The timezone defaults to New York if none is set. Restarts can also skip runs on older setups.
Does this sound like your situation?
- It works when I press Execute but nothing happens at the set time.
- It runs, but at the wrong hour.
- I changed the time and it still runs on the old one.
- It stopped running after the server restarted.
- Nobody knows if it ran last night.
Why does this happen?
A schedule needs a published workflow
Changes to a trigger interval apply only when the workflow is published. n8n says that after you change it, the change does not take effect until you unpublish the workflow and publish a new version. Variables used in the trigger are also evaluated only when it is published.
Confirmed by docs.n8n.io
The schedule starts from the moment of publishing
n8n gives an example: an hourly schedule changed to two hours and published at 11:30 runs next at 13:30, two hours after publishing, not at the next even hour.
Confirmed by docs.n8n.io
The timezone is not the one you think
If neither the workflow nor the instance has a timezone set, n8n defaults to EDT (New York). On self-hosted n8n the global timezone is set with the GENERIC_TIMEZONE variable, and each workflow can override it in its settings.
Confirmed by docs.n8n.io
Restarts can swallow a run on older setups
n8n says the older in-memory scheduler holds its timers in the process, so a stopped instance loses them and skips runs whose time passed during downtime. From n8n 2.45.0 a database-backed scheduler is on by default, and missed runs follow a misfire policy.
Confirmed by docs.n8n.io
Webhook tests behave differently from live use
For webhook workflows, n8n gives a Test URL, which stays active for 120 seconds while listening, and a separate Production URL that runs automatically only after the workflow is saved and published.
Confirmed by docs.n8n.io
What can I do about it today?
- Check the workflow is publishedLook at its status in the list. Do not press anything else yet.
- Look at the executions listSee when it last ran by itself, not by hand. The date tells you what changed.
- Note the hour you expectWrite it with your timezone. Compare with the timezone shown in the workflow settings.
- Ask what happened to the serverA restart, update or move near the day it stopped is a strong clue.
- Do not edit the interval to testEach change restarts the clock from the time of publishing, which can hide the original problem.
When should I bring someone in?
- The workflow handles invoices, reports or customer messages.
- It runs on some days and not others.
- You cannot see any scheduled execution in the list.
How do I handle it?
- Compare manual and scheduled runsI look at the last executions of each kind and at what differs: version, time and data.
- Check publication and settingsPublished state, interval, cron text and timezone at workflow and instance level.
- Check the instanceRestarts, version and which scheduler is in use.
- Fix and prove itI republish and watch for the next real scheduled run.
- Add a heartbeatAn alert if an expected run does not appear.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Does saving a workflow publish it?
No. n8n treats saving and publishing as separate steps.
Why did it run at midnight New York time?
n8n defaults to EDT when no timezone is configured.
Will a missed run catch up?
On n8n's durable scheduler it can, within a grace period; beyond that the misfire policy decides. On the older in-memory scheduler missed runs are skipped.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.