Scheduled triggers not executing properly

I’m having this issue as well. When I schedule a trigger the trigger is never executed and when I attempt to manually execute the trigger inside the workflow editor it operates as if it was running as a cron job and I am forced to wait for the duration of the timer delay before the workflow execute manually. Sometimes un publishing and republishing the workflow works to fix the problem sometimes I have to completely delete the schedule trigger node and that sometimes resolves the problem. But either way I’m consistently missing workflow automations because they’re not triggered at all and it’s causing a lot of issues

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:
1 Like

Hi @Chris_Warner Welcome!
I think you should try using the schedule trigger with Custom Cron expression instead of interval settings which really does not work in most cases, just make sure the workflow is published and also click on the 3 dots and go in settings and select the right timezone if that is not configured to your will, let me know how that performs.

Changing to use a custom cron fixed the manual execution of a scheduled trigger, that now works. I will post the results when I hit the requested interval time. Also, the timezone is correctly configured FWIW

1 Like

@Chris_Warner Glad it put some help although it should be working as it does in the published flows but let me know how that performs.

The cron job seems to have kicked off, but not until I

  1. switch to a custom cron setting
  2. publish
  3. change custom cron setting
  4. publish.

It seems to work now, but there are still issues as you can see.

1 Like

@Chris_Warner Yeah that is how that CRON JOB expression behaves, you need to publish it ofc: