If this is a bulk import report, send the spreadsheet to services@wildme.org with the email subject line matching your bug report
In which Wildbook did the issue occur? Zebra wildbook
What operating system were you using? (eg. MacOS 10.15.3) windows
What web browser were you using? (eg. Chrome 79) microsoft edge
What is your role on the site? (admin, researcher, etc) researcher
What happened?
Not loading match results
What did you expect to happen?
What are some steps we could take to reproduce the issue?
Hi @Rosemary
Can you please link to the encounter you’re having trouble with so I can look into this for you?
Wildbook
And my colleague John Naisike has the same problem since yesterday.
Thanks, @Rosemary!
It looks like the image analysis pipeline is completing the ID jobs but something’s preventing it from displaying the completed match results (though we can can see that they exist on the back end). We’ll need a little more time to work on this and I’ll share an update as soon as I can.
We’ve fixed the issue and are in the process of re-running the 660 match results that were affected. Thank you for reporting this!
Hi @Anastasia
Only the one I shared with you fetched results; the rest are stuck. Or we need to give it more time?
Wildbook
Hi @Rosemary
I spot-checked encounters from this import and I do see match results displaying now. I’m assuming these are the other encounters you’re referring to when you said the rest were stuck?
I did re-run matching on the encounter and I’ll check back today to make sure it completed.
I have checked from several encounters from Sept2024opc and Feb_march 2025 mpala imports and non is working.
Wildbook
Thanks for letting me know! I’ve been working with the devs to continue troubleshooting this. I’ll let you know as soon as things appear to be working properly!
Ok, this should be fixed for real now. Re-run any missing matches from these bulk imports and they should display correctly.
Here’s the match I re-ran from your earlier encounter link: Wildbook
It came back right away after this latest fix.
Thanks @Anastasia
I have tried a few and it’s working now.
1 Like