Hi @nukeador, welcome to the community and sorry for the trouble!
The RSS Feed Trigger trigger would be a polling trigger identifying already processed items based on the timestamp. So if polling fails (for example because of an unstable network connection), the trigger might miss some entries. The same would happen if entries appear in a given feed only with a delay.
For a more stable behaviour, perhaps you want to consider connecting n8n to a full RSS reader keeping track of the already processed items? This way you can (for example) fetch all unread items rather than items added since in the last polling interval, then mark them as read to prevent re-reading them. I’ve discussed possible approaches previously in this thread which you might find helpful.