Hi @accfish
This is a known bug that was resolved in Wildbook 10.3.0. When GrouperSpotter gets upgraded to the latest version, you’ll no longer see this issue.
In the meantime, you can manage its ID by editing the Identity section on the encounter page.