Timed Trigger doesnt Work

[turtle331]

For me the node is not fireing automated at all. Every time I activate it it fires all the rss that it missed but if I dont touch it, even if new rss is generated. The node is not triggering

[turtle331]

Thats the setting for one node,

This is the setting for the second node, same rss link but different last messages in Discord.

[turtle331]

This is for the first one

This is for the second node I posted

As you can see there is half a hour of difference, even though there should be only a time difference of maximum of 4 min

[turtle331]

For me the node is not fireing automated at all. Every time I activate it it fires all the rss that it missed but if I dont touch it, even if new rss is generated. The node is not triggering

Correction its firing but not at the time it should be

[Joffcom]

Hey @turtle331,

That is odd I am not seeing the same issue with my own workflows that are using the node.

What times are you expecting it to trigger and do you have a link handy for the feed you are working with? The sites I use don't post often so it could be something funky internally that I have not ran into yet.

[turtle331]

So I was doing some research with lorem Ipsum rss and found out some funny things
here is a collection of things:

Those are all the logs I collected, the n8n automation, which was responsible for that is this one:

[turtle331]

Ohh after I saved again I have another new behaviour

[turtle331]

Somehow every time I save I get a different behaviour

[turtle331]

This is my execution log for the workflow test

[Joffcom]

A lot of images there that make no real sense without some context.

Are your 4 triggers using the same 5 hour poll? The test rss site I think generates data as it is called.

Having 4 in the same workflow may cause issues as the node uses static data internally to track the last run time and it is key based so that could be why the runs are different. On manual execution the run time doesn’t get updated or checked as well so it is just the latest that gets returned.

If you split your test up into 4 workflows do you get the same issue and in your main workflow where you see the problem do you have more than one trigger node?

[turtle331]

A lot of images there that make no real sense without some context.

First of all I just dumped all the rss message triggers from your node to a discord node which relayed it to discord. The result of it is like the one I showed you. After that you see the node setup with the specific settings. Follwed by some interessting behaviour after a save. Fun Fact I never know what behaviour saving the automation brings. To round it up I also send all the execution logs of Test which is my testing automation with your rss triggers inside.

[turtle331]

Are your 4 triggers using the same 5 hour poll? The test rss site I think generates data as it is called.

Yes and No, I am using 4 triggers using the same 5 minutes trigger but my execution history tellls me otherwise.

[Joffcom]

Hey @turtle331,

What about when using only one trigger node in the workflow does that have the same issue for you?

[turtle331]

What about when using only one trigger node in the workflow does that have the same issue for you?

Yes, it does

[turtle331]

Having 4 in the same workflow may cause issues as the node uses static data internally to track the last run time and it is key based so that could be why the runs are different. On manual execution the run time doesn’t get updated or checked as well so it is just the latest that gets returned.

That was the final test I wanted to know, but then I discovered that there is a bigger problem. The polling is not triggering as it should.

[turtle331]

If you split your test up into 4 workflows do you get the same issue and in your main workflow where you see the problem do you have more than one trigger node?

I have the same issues in my main workflow.