I chatted with Jason Holmberg about this earlier today.
Here’s what we suspect: when someone draws a manual annotation in a mediaAsset containing multiple animals, the cloned encounter and the annotation to it might be inheriting some other weird match information.
Hi @MarkF - this is no longer a rare event. We’ve been seeing this multiple times a day and with multiple users. And with connectivity/performance issues, this is causing significant delays and negating the benefit of running detection + matching on import batches. Any chance this could get moved back up the priority list?
Hey @ACWadmin1 ,
This hasn’t really dropped off the high priority list; we’ve just had a couple of other emergent things take higher precedence. For example, we have a breaking issue with bulk import that has 3 people looking at it. Between that, vaccination, shift to colocation, and the rest, this is something that is still in high priority, but keeps getting bumped back to “not the biggest fire we have to put out”.
I’ll look to see if there’s anywhere we can refocus, but this is a bug I have been actively aware of since you reported it. I’m not sure what more we can commit to though.
Hi @tanyastere - sorry if I misunderstood @MarkF’s comment about priority and thanks for your reply. I thought it made sense to update the info on this issue as it relates to frequency. I know the team always makes best efforts and beyond to address issues and I know how priorities can shift as new issues crop up.
Rerunning matches is no longer resolving the issue and we are halted on matching for EWT Wild Dog census because I cannot put my user thru this. I personally went in and reran all of the matching on all of these encounters and the issue has not been resolved.
Please escalate the issue to the Max of your teams’ resources available.
Your issue I was fully able to reproduce and fix. It was caused by a fix for Safari deployed on Friday that went wrong. I rolled it back, and I was able to re-run all three of your examples and see the correct annotation displayed in the match results. So this is a separate issue from the running thread above and should now be resolved on ACW.