Encounter created by system not matchable?

[PaulK]

In which Wildbook did the issue occur?ACW

What operating system were you using? (eg. MacOS 10.15.3)Win 10

What web browser were you using? (eg. Chrome 79)Chrome

What is your role on the site? (admin, researcher, etc)Admin

What happened?
https://africancarnivore.wildbook.org/encounters/encounter.jsp?number=708fc95c-c5ed-40c7-b0ef-519703c8d657
Encounter of wild dog include body & tail but classified as not matcheable

Review of audit trail shows that this was not a manual annotation

Review of Audit Function : Check Annotation iaClasses and MediaAsset States by Species shows the following for AWD

What did you expect to happen?
I should be able to kick off matching
Inspection of Media Asset 89172 shows that I should be able to match against this annotation

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

If this is a bulk import report, send the spreadsheet to services@wildme.org with the email subject line matching your bug report

[jason]

Hi Paul,

I cannot reproduce. The annotation looks matchable already. I have seen situations like this soon after submission wherein detection has returned a bounding box but the cached object has not yet received its matchAgainst=true assignment, but the delay there is generally in the order of seconds. Generally one or two refreshes of the browser gets me to the point where cache and browser are in alignment.

In this case, it looks like the issue has resolved itself.

Thanks,
Jason

[PaulK]

I bet you cannot wait for 2.0

A lot of these syncing issues should disappear then as I understand it.

Thanks

Paul