Stuck in detection & identification

Support
,
1

What Wildbook are you working in? ACW

What is the entire URL out of the browser, exactly where the error occurred?
https://africancarnivore.wildbook.org/react/bulk-import-task?id=364410d5-a5a4-44f9-87c1-c288ecd1421c (detection not sent and button unavailable)

https://africancarnivore.wildbook.org/react/bulk-import-task?id=897f1a6b-ee86-43f8-bcf9-5c289f0d89e8 (stuck in identification at 50%)

https://africancarnivore.wildbook.org/react/bulk-import-task?id=91f6536a-b4aa-4972-ae07-61b8068e5473 (stuck in identification at 96%)

https://africancarnivore.wildbook.org/react/bulk-import-task?id=d484249b-2aeb-41c5-ba01-1062026c4d8d (stuck in identification at 66%)

https://africancarnivore.wildbook.org/react/bulk-import-task?id=d7e026f9-b3af-4ba3-9655-eca4a31bc452 (stuck in identification at 96%)

Can you describe what the issue is you’re experiencing?
All above links have been stuck in detection or identification for few days/weeks. Some of the encounters are still under “waiting to queue” although the batches have been uploaded 2 weeks ago.

Is it possible to avoid having identification sent automatically? Some images don’t have annotations and I would like to add the annotations and then resend the whole batch to identification at once rather than one at a time.
Also, the “send to identification” button is always grey (i.e. we can’t click on it)

Can you provide steps on how to reproduce what you’re experiencing?

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

2

Hi @Marine_Ingwe

Thanks for letting me know! We’re working on fixing the errors with detection and ID status. There are a few different layers impacting the status:

I had to send this one through detection using the old interface. Detection is now complete and you should be able to send it to ID now.

This is an error in the status. Every encounter in this import has a completed match. It’s just not reflecting correctly in the status.

Another status error, but this time in the class status. Two encounters are “waiting to queue” however neither of those encounters have annotations and aren’t actually waiting to be queued. I crossed-checked it in the old import interface and it shows up as complete there.

Ditto above. It’s treating the encounters without annotations as waiting to complete ID, even though those are skipped for ID jobs. The old import interface verifies that this import completed ID: https://africancarnivore.wildbook.org/import.jsp?taskId=d484249b-2aeb-41c5-ba01-1062026c4d8d

This is an error in the status. Every encounter in this import has a completed match. It’s just not reflecting correctly in the status.