When a campaign finds an item that was already published, WPeMatico stops reading the feed and ends that run. This is the expected behavior and, in most cases, the best one. This FAQ explains why it happens and when to use the Continue Fetching if found duplicated items option (previously named Jump Duplicates) to change it.

Feeds list the newest items first.

Almost every feed lists its items by date, from the newest to the oldest, and the campaign reads them in that order. When it finds an item that was already published, all the items below it are older, so they were already fetched in previous runs. Stopping there saves time and server resources.

Example: a feed has 10 items and the campaign creates 4 posts per run. The first run publishes the 4 newest items and leaves out the other 6, but this happens only the first time. From then on, each run publishes the new items until it reaches the first one that was already published. If the campaign runs often enough, it will not miss any item.

Skip each duplicate and keep reading the feed.

With this option enabled, the campaign does not stop at the first duplicate: it skips it and keeps reading the rest of the feed, looking for items that were not published yet. It can be useful with feeds that do not list their items by date.

To enable it for all campaigns, go to WPeMatico → Settings and check Continue Fetching if found duplicated items in the Advanced Fetching box.

To enable it only for one campaign, edit it, check Don’t use general Settings in the Duplicate controls box and then check the same option there.

Note: This option is not recommended for most feeds. Every run reads the whole feed, which uses more resources, and on feeds where the duplicate check by title does not work well it may publish the same item twice.

Run the campaign often enough.

Instead of enabling this option, adjust the campaign to the pace of the source site:

• Check how many new items the source publishes per hour or per day.
• Schedule the campaign to run more often than that, in its Schedule Cron box. See How to use Cron Scheduling?
• Set Max items per fetch, in the Options for this campaign box, a little above the number of items the source publishes between two runs. Lower values give better performance.

For example, if the source publishes about 10 items a day, running the campaign every hour with 2 items per fetch is enough. If it may publish more than 2 items in an hour, run it every 30 minutes.

Note: If you use the Custom Title feature of WPeMatico Professional, the duplicate check by title cannot recognize the items, because the saved title is different from the original one. The check by hash keeps working.

To learn how the duplicate controls work and how to adjust them, see How to control duplicate posts?