Knowledge base · 05

Memory duplicates and conflicts

Choose what to do when an entry with the same Source already exists.

← Memory & terminology Updated: 2026-08-12

When saving, Polyframe checks whether Memory already has an entry with the same type, language and normalized Source.

If it finds a duplicate, you can choose:

  • Replace existing - remove the found duplicates and save the new version;
  • Add anyway - keep both entries;
  • Cancel - do not save the change.

Replacing is usually best when the new Target is a corrected version. Add anyway only when you intentionally need variants.

With several active Blocks for the same source, matching prefers the most used entry, then the newest one. This can make results harder to predict, so it is better to clean up duplicates.

A memory language mismatch is not a duplicate. You can edit that memory, but Blocks will not match the active project language.

Before deleting many entries, create a TSV export.

After cleaning the memory, check project quality markers.