In this article
Feed caching is delaying updates
Your feed is missing GUIDs
Your feed contains duplicate GUIDs
You've hit a posting rate limit
1. Feed caching is delaying updates
If dlvr.it isn't seeing new items as quickly as expected, your RSS feed may be cached on your server. Caching reduces server load, but it can also mean that feed updates aren't served out to dlvr.it right away — sometimes causing delays of several hours or more.
What to do: Check your cache plugin settings and look for an option to either exclude RSS feeds from caching or reduce the cache expiry time for feeds. If you're not sure how to adjust this, your system administrator or hosting provider should be able to help.
📸 [Screenshot: Example of a cache plugin settings screen showing RSS feed cache options]
2. Your feed is missing GUIDs
This is one of the most common causes. dlvr.it uses an item's GUID (Globally Unique Identifier) to determine whether it has seen that item before. If your feed doesn't include GUIDs, dlvr.it falls back to using the item's URL instead.
If all your items share the same URL — for example, if your feed always links to your homepage rather than individual posts — dlvr.it will see each new item as the same item it already posted, and won't publish anything new.
What is a GUID? A GUID is a unique string assigned to each item in an RSS feed. Feed readers like dlvr.it use it to identify which items are new. A GUID can be a URL, but only if that URL is unique to each item. If new content is regularly published at the same URL (such as a weather update page), a non-URL string is a better choice. Once assigned, a GUID should never change for that item.
There are three ways to resolve this:
Add GUID fields to your feed with a unique value for each item. This is the cleanest fix and is worth doing if you have control over how your feed is generated.
Link to individual posts rather than your homepage or a shared URL. This gives each item a unique URL that dlvr.it can use as an identifier.
Enable "Re-post items with updated timestamps" in dlvr.it. Go to your Feed settings, open the Advanced tab, and turn on this option. dlvr.it will then use the item's timestamp as a signal for new content.
Heads up: The "Re-post items with updated timestamps" setting can cause duplicate posts if your feed timestamps update without the content actually changing. Use it as a workaround, not a permanent replacement for proper GUIDs.
📸 [Screenshot: dlvr.it Feed settings — Advanced tab, showing the "Re-post items with updated timestamps" toggle]
3. Your feed contains duplicate GUIDs
The reverse problem can also occur: if your feed publishes a new item but assigns it a GUID that dlvr.it has already seen, dlvr.it will treat it as an old item and skip it.
What to do: Enable "Re-post items with updated timestamps" in your Feed settings (Advanced tab). With this setting on, dlvr.it will check for a new timestamp on each item and republish any item whose timestamp has changed — even if the GUID looks familiar.
As above, use this setting with care if your timestamps change independently of your content.
4. You've hit a posting rate limit
If your feed is working correctly but posts are still not going out, you may have reached the posting rate limit for one of your connected social accounts. Each platform sets its own limits on how many posts can be published within a given time window.
See Supported channels in dlvr.it for details on rate limits for specific platforms, or check your dlvr.it feed log for any error messages related to rate limiting.
📸 [Screenshot: dlvr.it feed log showing a rate limit error message]
Still not seeing new items post after checking all of the above? Reach out to our support team at [email protected] with your feed URL and we'll take a look.