N8N SCHEDULES

n8n Schedule Trigger not running: the five things to check

Short answer: a Schedule Trigger only runs for a workflow that has been saved and published. If you changed the interval or a variable after publishing, the change does not take effect until you unpublish and publish again. If it runs at the wrong hour, the timezone is the first suspect. If it never runs, check the cron expression.

All of this comes from n8n's own documentation for the Schedule Trigger node and its common issues page. Current n8n docs say "publish". If your n8n screen says "Active" instead, read "publish" below as "active".

Step 1: is the workflow published?

n8n's docs put this in a callout: if a workflow uses the Schedule node as a trigger, save and publish it. Check that your workflow shows as published (or active) in your n8n.

Step 2: you changed it after publishing

This is the one people miss. n8n says you can update the trigger interval at any time, but the change only applies when the workflow is published. If you changed the interval after publishing, it does not take effect until you unpublish the workflow and publish a new version.

The same applies to variables used in the schedule. Their values are only read when the workflow is published. Change a variable in settings afterwards and the schedule does not follow. Unpublish, then publish again.

There is a timing detail too. n8n says the schedule begins from the time you publish. Its example: you had every 1 hour, expected at 12:00, then changed it to every 2 hours and published a new version at 11:30. The next run is 13:30, two hours after you published, not the next round hour.

Step 3: the timezone

If the workflow runs at the wrong time of day, n8n says to adjust the timezone. The node uses the workflow timezone if one is set. If not, it uses the n8n instance timezone. n8n documents the default instance timezone as America/New York for self-hosted instances. On n8n Cloud, n8n tries to detect the owner's timezone when they sign up and falls back to GMT.

To set it for one workflow: open the workflow, click the three dots in the upper right, choose Settings, change Timezone, and save.

To set it globally: on Cloud, follow n8n's page for setting the Cloud instance timezone (admins can change it in the Admin dashboard). If you host n8n yourself, set the GENERIC_TIMEZONE environment variable.

A schedule written for 9:00 and a server set to another zone will run at 9:00 in that zone. If your team is in a different region, set it per workflow.

Step 4: the interval itself

For the Hours, Days, Weeks and Months options, check the fields n8n asks for. A few that catch people:

• Months: the Trigger at Day of Month field takes 1 to 31, and if a month does not have that day, the node does not trigger. n8n's example: enter 30 and it will not run in February.
• Hours: Hours Between Triggers plus Trigger at Minute. Six hours and minute 30 means every six hours at 30 minutes past.
• Weeks: you choose the weekdays as well as how many weeks between runs.

You can also add several Trigger Rules to one node to run on different schedules.

Step 5: a cron expression that is invalid

If you use Custom (Cron) and see an Invalid cron expression error, n8n says there is a mistake or incompatible syntax. It suggests two checks: compare with the cron examples in its docs, and paste the expression into crontab guru after removing the seconds column to see if it validates.

The seconds field is optional. n8n's docs explain that the sixth asterisk is seconds, and the node runs even if you do not set it. Its examples include */5 * * * * for every 5 minutes, 0 6 * * * for 6:00 AM daily and 0 9 * * 1-5 for 9:00 AM on weekdays.

If you are unsure, use the Minutes or Hours option instead of an expression. That advice is ours, not n8n's.

What we cannot tell you from the docs

n8n's pages do not cover what happens if your n8n server restarts at the scheduled time, or other hosting problems such as a stopped container. If your n8n is self-hosted and the checks above are fine, check that the server was actually running when the schedule was due.

When to hire help

Ask for help when the schedule looks right but nothing runs, when you run n8n yourself and the problem seems to be the server, or when missed runs mean missed invoices, reports or customer emails. Tell us whether you use n8n Cloud or host it yourself, your timezone, the schedule you want and the last time it ran. We will tell you what we found and agree the price first. One defined defect is a fixed $299, with the $99 diagnosis credited. Larger work gets a written quote. We never ask for your password: tell us what is happening.

If it is a webhook and not a schedule that is giving you trouble, that is a separate set of checks, since n8n webhooks have different test and production URLs.