ConvertKit RSS-to-email delay: when feed items skip a send

a person typing on a laptop keyboard on a desk

The newsletter for newsletter operators

Daily field notes on deliverability, AI tools, hosting, and monetisation. No "top 10 plugins" filler — real tools, real numbers, real failures.

ConvertKit RSS-to-email delay: when feed items skip a send
Photo by Kit (formerly ConvertKit) on Unsplash

ConvertKit’s RSS-to-email automation is a one-click bridge between your blog and your subscribers’ inboxes. You paste in a feed URL, pick a template, set a schedule, and ConvertKit promises to email your list every time you publish. Except it doesn’t always fire when you expect it to—and understanding the polling window is the difference between a post reaching inboxes within the hour and disappearing entirely.

ConvertKit polls RSS feeds every 60 minutes

ConvertKit checks your RSS feed once per hour, on the hour, starting from the moment you activate the automation. If you turn on RSS-to-email at 9:14 AM, ConvertKit will poll at 10:14, 11:14, 12:14, and so on. The official documentation (checked November 2026) confirms the 60-minute interval but doesn’t surface the edge case: items published between polling windows can be skipped if they’re no longer the most recent item by the next check.

Say you publish a post at 10:30 AM. ConvertKit polls at 10:14 and sees nothing new. At 11:14, it polls again and finds your 10:30 post—it queues the email. But if you publish two posts in quick succession—one at 10:30 and another at 10:50—ConvertKit’s 11:14 poll will see only the 10:50 item as the newest entry. The 10:30 post never triggers a send unless it was already in the feed during the previous check.

When rapid publishing breaks the automation

This isn’t hypothetical. Solo operators who batch-publish—say, uploading three posts at once after a weekend writing sprint—will see ConvertKit email only the last item in the feed. The earlier two vanish from the automation’s perspective because ConvertKit doesn’t store a history of items it’s already seen; it compares the current feed state against the previous poll and sends whatever’s new at the top.

WordPress users hit this more often than expected. If you schedule three posts to go live at 8:00, 8:15, and 8:30 AM, and ConvertKit polls at 8:45, it sees only the 8:30 post. The others are buried below the fold in the feed and never enter the send queue. ConvertKit’s RSS parser reads the feed’s <item> nodes in order and considers only items that weren’t present in the last poll and are still near the top of the feed.

The workarounds that actually work

Space your posts at least 90 minutes apart if RSS-to-email is your primary distribution channel. That ensures each item gets at least one full polling window where it’s the newest entry. If you publish at 9:00 AM, wait until 10:30 or later for the next post—giving ConvertKit’s 10:14 poll time to catch the first item and the 11:14 poll time to catch the second.

Alternatively, limit your RSS feed to one item. Most feed plugins let you set a post count; dropping it to one forces every new post to occupy the top slot until the next publish. ConvertKit will never miss an item because there’s nothing to displace it. The tradeoff: readers who subscribe to your feed directly in an RSS reader see only your latest post, not a backlog. For operators who use RSS exclusively as a newsletter trigger, that’s fine.

If you’re on WordPress and using Jetpack or a similar feed-caching plugin, flush the feed cache immediately after publish. ConvertKit can only see what your server serves; if your feed is cached for 60 minutes and you publish at 10:05, ConvertKit’s 10:14 poll may still see the old feed. Clearing the cache ensures the new item appears in time for the next poll.

The non-obvious detail: ConvertKit doesn’t retry

Once ConvertKit skips an item, it’s gone. There’s no manual “re-check feed” button in the UI, and support won’t trigger a retroactive send. If an item was present during a poll but didn’t rank as new, it won’t reappear in future checks. The only recovery path is to disable the RSS automation, wait five minutes, re-enable it, and hope the item is still near the top of the feed when the next poll runs.

That delay matters for time-sensitive content. If you’re publishing news commentary or event recaps, a 90-minute gap between publish and send can bury the story. In those cases, skip RSS automation entirely and use ConvertKit’s broadcast feature to send manually. The control cost is two minutes per post; the upside is guaranteed delivery within seconds of publish.

Want more tool mechanics like this? Subscribe to One Two Three Send—we explain the gaps in the documentation so you spend less time troubleshooting and more time building.

The newsletter for newsletter operators

Daily field notes on deliverability, AI tools, hosting, and monetisation. No "top 10 plugins" filler — real tools, real numbers, real failures.

Other newsletters you might like

Irish Rugby Fans

The best Irish rugby updates, straight to your inbox — Six Nations, the Nations Championship and the provinces. Only when there's something worth reading.

Subscribe

Love California

Love California — in your inbox The Pacific Coast Highway, national parks, beaches, wine country and the best places to visit in California. One short email, every day.

Subscribe

Springbokfans

The best Springbok updates, straight to your inbox. Only when something worth reading actually happens.

Subscribe

Love Spain

Love Spain — in your inbox. Iconic cities, hidden pueblos and the best places to visit in Spain. One short email, every day.

Subscribe

Newsletters via the One Two Three Send network.  ·  Want your newsletter featured here? Click here