Then, after waiting for the new match results, I’ve gotten an “attempting to fetch results” in all cases this afternoon. Refreshing the page multiple times has not helped.
What did you expect to happen?
I thought this issue was fixed - per the January release notes:
" * WB-1252 No more 400 Python errors (IAResults inspect) on new-and-very-likely matches
So I expected to be able to “inspect” the match results and see the 2 images side by side with hotspotter patches on the matched areas.
Hi, @ACWadmin1 !
I was unable to reproduce this issue just now when I checked, but I experienced the same thing earlier today on ACW.
When I had my same issue, I checked and saw that there were quite a few IA jobs in the queue; my best guess is that this is what was going on, as all of those jobs have been completed now and results are displaying just fine.
Apologies for whatever it was that caused this, but seems to be working okay now…
My best,
Mark
Regarding the 400 python errors, I’ll ask the IA folks again right now; I know someone was looking into it yesterday, but I’m not sure what the conclusion was.
-Mark
These match results are from April and May 2021
After 90 days, the ID comparison renders are deleted in WBIA to save space
even the job is archived after 2 weeks
Basically, they are trying to look at old matching jobs and WBIA has deleted the cached results…
It also prevents the need to link to the backend WBIA instance and its URL
We’ve run into this in the past, it’s certainly expected behavior across all WB projects.
if they were to resubmit the ID job, everything would work.
So, that’s the workaround. I will create a ticket to improve the UI so that the user doesn’t expect one thing and see an error instead asap.
Thanks,
Mark
Go to match result #8 and click on inspect. You’ll see what I mean. It’s a really GREAT match and I really want to get the hotspot inspect compare to use for demo purposes.
Thoughts? Do I need to re-run this encounter again?
Hi @mark - okay, I understand now. the blowing out of the cache isn’t a strict ‘everything older than 90 days’, it’s a ‘whenever the cache is full-ish’, which makes sense. We’ll update our workflow with our users - upload & process through IA smaller batches so they can be ID’d more quickly before a new batch is uploaded.
