Skip to content

RSS troubleshooting

When an auto feed stops posting, posts the same thing twice, or shares the wrong items, this page helps you fix it fast.

Why use it

Auto feeds run on their own, so when something looks off you need a quick way to spot the cause. These three checks solve almost every case.

Step by step

Check the feed address works

Open the feed address in a new browser tab.

  • If you see text or a list of articles, the address is fine.
  • If you see an error or an empty page, the address is broken. Fix the address in your feed, then save.

Check the channel is still connected

Open the feed's settings and look at the channel it posts to.

If the channel shows as disconnected, reconnect it, then pick it again for this feed.

Re-run the feed

Save your changes and run the feed again.

Watch the next post. If it goes out correctly, you're done.

TIP

Seeing the same item posted twice? This usually means the source changed the item's hidden ID. Wait for the next fresh item, then re-run, and it should settle.

Good to know

  • A feed that suddenly stops is most often a broken address, a disconnected channel, or a feed page that won't load properly.
  • Duplicates happen when the source keeps changing the unique ID it gives each item.
  • A feed only posts genuinely new items, so if nothing new appeared at the source, nothing will go out.
  • If your plan no longer includes auto feeds, they stop running. Check your plan if everything else looks correct.
For developers
  • Feeds behind HTTP basic auth need credentials in the schedule's data JSON; the default rss-parser config does not carry them.
  • Non-UTF-8 feeds (Windows-1252, ISO-8859-9) are usually handled, but malformed XML stops the parser. The last error is stored in stats.
  • Deduplication uses the entry GUID. If the source mutates GUIDs between updates, dedup breaks — lock the GUID upstream or filter by <link> (see the per-feed data JSON for the hash strategy).
  • Items only post when stats shows new entries, the schedule's accounts are still valid channels, and the workspace plan still has the posts.rss feature.