If a duplicate is found in history the new nzb is added to history with status DUPE or COPY. However if a duplicate exist in
hidden history only (and not in visible history) the duplicate isn't added to history at all.
The reason is: let's assume you have an RSS for certain show. The same episodes are reposted again all the time. You would have your history constantly filled with DUPE-items for episodes you downloaded months or years before for which you don't really care anymore (they are long in your library or are watched).
With current behaviour the new aired episodes are added to queue and downloaded. Duplicates are added to history with DUPE status. After
KeepHistory days (30 by default) the successfully downloaded nzb transits into hidden state. After that all new nzbs for the same episode will be ignored. Isn't that nice?
There is also a possibility to force ignoring to happen sooner than KeepHistory days. For that user can mark item in history as GOOD which for NZBGet means that the title isn't needed anymore and shouldn't be watched.
In your case I think it would be better to disable duplicate check for items coming from Bookmark feed. You can do that by setting dupemode=force in the filter of that feed:
Statuses:
- Dupe - the nzb was deleted by duplicate check. Because there is another item in queue. The item with status "Dupe" maybe used automatically if the item which is in queue fails.
- Good - the nzb was marked as good by user using command "Mark as good" in history dialog. Any new arrived duplicates will be ignored (not added to queue nor to history).
- Copy - the nzb was deleted by duplicate check because this nzb-file already exists in download queue or in history. Here the nzb is the exactly same copy of another nzb. This status can occur only if you try to add the same nzb again. The exact content of nzb is compared here (via article IDs).
I have to review and update the documentation page for RSS as it seems to miss some infos.