I setup a simple workflow which supposed to be triggered by RSS Trigger, but it does not work unless I manually run it. I set it to active and made sure to set the polling time. do I need to set anything else to make it run based on the poll time that I set?
Information on your n8n setup
**n8n version: 1.20.0
**Database (default: SQLite):Default on cloud
**n8n EXECUTIONS_PROCESS setting (default: own, main):Default on cloud
**Running n8n via (Docker, npm, n8n cloud, desktop app): Default on cloud
Hi @yoventures, I am sorry you are having trouble. Is there a chance that your feed is publishing new articles only with a delay and backdated timestamps, as rss.app appears to be a website scraping service?
If so, this node may not be suitable for your particular use case. This is because the node will compare the timestamp of each feed item with the last polling time. You may instead want to consider using a full RSS reader coming with an API. Unlike n8n, RSS readers maintain a database of all the feed items they encounter, so you can, for example, retrieve all unread items regardless of when they were added to a feed.
I wrote about this a while back over here, perhaps you find this thread helpful.
I have tried to port some RSS sources to the new RSS Feed Trigger Node. Most of the RSS feeds work normally, but a small portion of them keep fetching summaries repeatedly.
The reason I chose feedgen is because I want to read the full text XD
I want to understand what causes the source from feedgen to trigger repeatedly when fetched
What version of n8n are you running? We recently fixed an issue with the trigger node where it wouldn’t grab everything but it should now grab everything based on the dates.
After I updated to 1.29.1, the RSS Feed Trigger Node still repeatedly fetches content. I noticed that feedgen, unlike traditional RSS, does not put the latest content at the top when updating, but puts it at the bottom. Could this be related to it repeatedly fetching content?
–
I tried other RSS feeds that also had problems in the old version, like this one: Blog | Daily Oops!. It is now working well ! so could it be a problem with feedgen not conforming to the standard?
The node will fetch everything it can then use the publish date to work out what is new, It could be that the dates are not taking timezones into consideration in the feed though as looking at it there are future dates but no timezone offset so this would result in you always seeing the future posts.
I have additionally tried several other feedgen links and found that as long as conditions are added, the results obtained will not trigger repeatedly. https://feedgen.org/ptt?b=Stock&q=recommend:30
It seems that this has nothing to do with the time zone. The reason for seeing future times is because the time zone set by feedgen (UTC) is different from the time zone used by the article author (UTC+8).
I believe there is no issue with this Node, as the lastItemDate it stores is indeed based on the time of the ‘last item of data’. The future time you mentioned is actually a sorting issue, which this Node can accurately record.
The problem lies in certain situations where feedgen returns a sorting order that is different from the regular RSS. Because it places new data at the end, while normally RSS is set in reverse, this causes the node to regard the top data (the oldest time in the list) as lastItemDate, leading to all items in the table being fetched every time it runs.
If feedgen’s sorting is normal, this problem will not occur.
Thank you for your reply! And for the n8n-nodes-rss-feed-trigger you made for the community, it has helped me simplify many workflows!