Differences between n8n doc and n8n node explanation


Hello everyone!
I have difficulty with the cron (schedule trigger)
1/ I don’t understand why there are differences between your doc and the node explanation. Which is the good one? (cf first 2 pictures)
2/I want my wf to be triggered the 3rd of each month at noon (BUT not march, june, september and december). I don’t know why the wf has been triggered June 15th at 12:00
I used Cron expression = 0 12 3 * 1,2,4,5,7,8,10,11
3/ On the other way around, I want another workflow to be triggered the 3rd of march, june, september and december at 12:00
Cron expression = 0 12 3 * 1,2,4,5,7,8,10,11
And this one work. Why not the previous one? It’s exactly the same format…

Thanks a million for your answers, team!

Hey @Gregoire_Hamille,

This caught me out the other day, The docs is the correct option we support the extra second option. We recently fixed an issue with the schedule node which I think will fix the issue you are seeing it might be worth making sure you are on 0.231.2 or later and seeing if that works.

1 Like

Thanks, @Jon
My CTO tried to upgrade to 0.231.2 but it didn’t work (see logs below)


Can you help us with that?

(We had to downgrade to 0.202.0 for now until the issue is fixed)

Hey @Gregoire_Hamille,

That looks like the migration was taking time, I would either clear out some old data if you are using SQLite or let the migration process finish.

Mmmh ok we’ll try, that’s a bit annoying.
Thanks a million for your answers @Jon , I’ll keep you posted

1 Like

Hi @Jon It seems that it’s not a matter of time, the query is not taking long. See the screenshot below

Hey @Gregoire_Hamille,

It can crash if it is trying to do something and runs out of memory, Can you give me more information on your set up? It does look like it is still trying to go through the migrations before it crashes but it is a bit slow.

Hi @Jon

Its a Docker container that uses the official n8n Docker image. Here’s the config:
version: “3.1”

services:
n8n:
image: n8nio/n8n:0.231.2
ports:
- 5678:5678
volumes:
- $PWD/.n8n:/home/node/.n8n
restart: always

Cheers

Hey @Gregoire_Hamille,

That looks like it should be fine, What is the size of the database at the moment?

@Jon not sure I got it, we don’t have a database for n8n

@Jon Or are you talking about the size of the execution folder?

Hey @Gregoire_Hamille,

n8n will have a sqlite database that contains all of the data, Looking at your config it would be in $PWD/.n8n

Hi @Jon
I just checked with my CTO, the size of the folder is 6.1GB

Hey @Gregoire_Hamille,

So it could be that the migration is taking time or maybe there is not enough space to fully carry it out, I would suggest rolling back to a previous version of n8n that worked and enable the data pruning options to remove some of the older data.

Thanks for the quick answer @Jon

enable the data pruning options to remove some of the older data

How do we do that? Can you share with us the lines to write in the terminal?

Hey @Gregoire_Hamille,

It is done through the environment options that are in the link I shared above.

Hi @Jon
We upgraded n8n to 0.231.2 and my cron is still not working
I want my wf to be triggered the 3rd of each month at noon (BUT not march, june, september and december)
I used Cron expression = 0 12 3 * 1,2,4,5,7,8,10,11
I don’t understand why my cron is triggered everyday at noon, and whatever the month.
Any idea?

Thanks

Hey @Gregoire_Hamille,

To me it looks like the cron isn’t correct, Have you tried 0 0 12 3 * 1,2,4,5,7,8,10,11

@Jon still not working,
The wf has been triggered again today at 12 :thinking:

@Jon could we have some help on that? we followed carefully the doc and the cron is still not working