Schedule node not executing (n8n cloud)

Questions
,
1

Hi guys, I’m having issues with a scheduled workflow not running, but another exact copy of it does.

In the executions log, there are no attempted or failed executions, other than 1 success on the 14th March when it was first set up.

It’s hosted on n8n cloud.

Describe the issue/error/question

  • I have a workflow with a schedule trigger, but it doesn’t run on schedule
  • The workflow is switched to active
  • It’s a copy of another workflow, which works correctly

What is the error message (if any)?

  • There are no attempted or failed executions, other than 1 success on the 14th March when it was first set up

Please share the workflow

Share the output returned by the last node

n/a

Information on your n8n setup

  • n8n version: 0.219.1
  • Database you’re using (default: SQLite): n8n cloud
  • Running n8n with the execution process [own(default), main]: n8n cloud
  • Running n8n via [Docker, npm, n8n.cloud, desktop app]: n8n cloud
2

I am very sorry for the trouble. I’ve seen a few of reports about this trigger not doing exactly what it should by now, but so far I wasn’t able to reproduce these problems (just like in your case my own copies of such workflows are running fine).

Is there a chance this workflow is actually running but you’re simply not storing successful executions for it?

3

Good shout, but I’ve got “Save successful production executions” enabled and on the successful execution on the 14th, it logged the success.

1 Like
4

Hm, perhaps @agobrecht has an idea on that one? I know he worked a lot on this node a while back.

5

The cron expression looks wrong:

0 1 * * TUE-SUN

Weekdays are normally numbers. So it should probably loook like this:

0 1 * * 0,2-6

fyi we use this library underneath the hood:

And you can use the crontab.guru for testing them. Here for the one above:

1 Like
6

Hi @jan, do you have any idea why a copy of the workflow shared by @ChrisTrunk would work?

Hi guys, I’m having issues with a scheduled workflow not running, but another exact copy of it does.

This is what really threw me off here.

7

The Scheduler Node is using Static Data, it’s probably why duplicating the node breaks the node. I’ll make a ticket internally about it.

1 Like
8

The Scheduler Node is using Static Data, it’s probably why duplicating the node breaks the node. I’ll make a ticket internally about it.

Does that mean if I delete the Scheduler Node and add a new one with the same settings, it’ll work?

9

@MutedJam Me also, but sadly not. I would expect that none of them works, honestly.

@agobrecht @ChrisTrunk can not imagine that there is any problem regarding static data. After all, is it totally separated per workflow and then also per node. If the code is written so that it can handle that no data is there yet (as it would also happen literally every time you create a new node), it should work.

1 Like
10

My bad I thought that @ChrisTrunk was using the weekly interval, I tested it locally and the library does support the DAY format, however the DAY-DAY format is not supported, it would only trigger on the first day in this case TUE.

2 Likes
11

Great @agobrecht that would then explain it as the day it was set up and was working (the 14th of March) was a Tuesday.

12

Some of this conversation is over my head, but is there anything I can try to do to get my workflow going on schedule?

13

I think @jan’s original suggestion should do the trick:

So simply replace TUE-SUN in you current cron expression with 0,2-6 and you should have a valid cron expression working with the node :slight_smile:

14

This did the trick, thank you!

1 Like
15

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.