Error processing both sides

In which Wildbook did the issue occur?
Internet of turtle
What operating system were you using? (eg. MacOS 10.15.3)
Windows 10 Pro, 64 bits

What web browser were you using? (eg. Chrome 79)
Chrome 113.0.5672.93. 64 bits
What is your role on the site? (admin, researcher, etc)
What happened?
in encounters with two sides, comparisons are being made with only one side and when the other side rotates, it appears as a new individual. it’s normal? and how to proceed with the side that did not appear during the analyzes. I tried it on 2 different days and the same problem continued with the generated individual " Occurrence ID: mdt374 612b47a2-3801-489c-9756-8392c3ddda71]

What did you expect to happen?
I imagined that the two sides should appear, each with their possible compatibility together, on the same page

What are some steps we could take to reproduce the issue?

If this is a bulk import report, send the spreadsheet to with the email subject line matching your bug report

Hi @maria

Only annotations with the same viewpoints are matched against each other. For example, right viewpoints are matched with other right viewpoints. It’s possible that there aren’t any confirmed matches from its other side yet for it to be offered as a match candidate. This is the expected behavior.

Good afternoon. separately the two sides show results of possible compatibilities. The two sides of the encounter do not appear together in the Matching results, when run one after the other the system offers the possibility of updating the individual’s code to the next number in the sequence, which is the same individual.
this compared to a region (Brazil-Arraial do Cabo) that has hundreds of images on both sides.

This sounds similar to what’s happening in this post. My recommendation is to manually name your new individuals for the time being until the bug is resolved.

Here’s the link to the ticket where we’re tracking the issue of duplicate individuals being created: Duplicate individuals can be created when an encounter deleted from a project is assigned an already-existing individual name · Issue #257 · WildMeOrg/Wildbook · GitHub

Updated to edit ticket link. Previous ticket was related to duplicate IDs created during the bulk import process. We have a separate ticket to track duplicate IDs related to Confirm no match in projects.