Workflow with RSS feed trigger missed new item
Status: Open · Asked by jonbstrong on · 0 views
I’m seeing an issue with the RSS “New Item in Feed” trigger where a specific entry from a YouTube feed was skipped, even though other items before were processed correctly.
Feed:
https://www.youtube.com/feeds/videos.xml?channel_id=UC_085z9w4c7hPdZtZFRHUtg

- The workflow has successfully triggered for multiple items (see task history)

- However, the most recent entry was never triggered
I need to ensure that every new item in the feed is captured reliably, with no missed entries.
Hi @jonbstrong,
We have forwarded this concern to our technical team. Please allow us some time to look into it. We will get back to you with an update soon.
Thanks & Regards,
Arshil Ahmad
Customer Support Associate
? Pabbly.com
Hi @jonbstrong,
Thank you for your patience.
We are currently unable to access the RSS feed link you shared. It appears there may be some restriction on it.
Could you please check and ensure that the feed is publicly accessible? Once it is accessible, we’ll be able to investigate this further.
Apologies, this feed url I shared was incorrect, it's actually:
https://www.youtube.com/feeds/videos.xml?channel_id=UC_O85z9w4c7hPdZtZFRHUtg
Thank you for sharing the Feed URL. Our team is looking into this concern and will get back to you as soon as we have any updates.
Thanks & Regards,
Arshil Ahmad
Customer Support Associate
? Pabbly.com
Hi @jonbstrong,
Thank you for your patience.
We request you to please confirm if you have observed any other instances where an RSS feed item did not trigger the workflow.
Our team has checked this thoroughly, and there does not appear to be any platform-specific issue, as the RSS trigger is working correctly for other users. However, we did notice inconsistency with the accessibility of your RSS feed URL:
- It was accessible on Saturday
- It was not accessible on Monday
- It became accessible again on Tuesday
This suggests that at the time the item was published, the feed might have been temporarily unavailable or facing access issues. Due to this, the workflow likely missed that particular item.
Kindly monitor this further, and if you notice similar instances again, please let us know so we can investigate deeper.