I chatted with the team about this one, and apparently we’re already working on a ticket internally to improve exactly this behavior: WB-1440.
The related post and advice for that user can be found here: iaResults showing all results from import
The advice Tanya gave last time was:
"Some news. The short of it is:
We figured out the issue, and we’re in the middle of fixing it.
The long of it is:
If you send a bulk import task to identification, it runs all of the match jobs as a single job. If you do a smallish import, this is something that can go unnoticed, but if you do an import of more than 100, it makes the page slow and hard to load.
We are fixing this by making bulk import ID jobs run as individual jobs.
What you can do as we work on this fix: manually run ID jobs.
Go to the encounter, go to the gallery, click the hamburger menu, and click ‘start new match’. This will create a single match job that will not crash the page."
Hi Mark, we may need to re-open this ticket I’m afraid.
I’ve re-uploaded some photos via bulk and am having another issue when attempting to view the match results - the error “there was an error parsing results for task 4dc13c87-a93e-4cab-9d71-5dcb95ecd308” occurs.