Inconsistent errors during detection and matching "attempting to fetch results"

Bug Reports
,
1

In which Wildbook did the issue occur? - Flukebook

What operating system were you using? Windows 11 Home
Version 25H2

What web browser were you using? Chrome Version 146.0.7680.153 (Official Build) (64-bit)

What is your role on the site? - Researcher

What happened?

I have had several incidences when the programme would detect the fluke in a submitted encounter, but the annotation would not be complete for matching. (All encounters are individual encounters, not a bulk import.) I include an example below:

https://www.flukebook.org/react/encounter?number=2775a638-7c46-4bc4-b2a6-4fadff1461b8

I have added another annotation manually to some encounters when I had this problem, to then try to do the matching. Below I include an example, however now I am receiving the “attempting to fetch results” error. https://www.flukebook.org/react/encounter?number=2a1f476d-9845-40c7-b7f9-ee683a9d8289

I have also been having a few errors during the matching phase that usually would be solved by refreshing the page, however I have recently come across the encounter below that is stuck with the message “attempting to fetch results” and “there was an error parsing results”. Below are two examples.

Please can you help to work out what the problem is here.

Many thanks, Ruth

2

Thanks for the examples! I’ll need more time to work on this. There is definitely some unusual behavior I see that I’ve not run into before.

1 Like
3

Regarding this encounter, my recommendation is to delete the photo from the encounter (click on the photo and then click on the Delete Image button) and then upload it again so you don’t have to re-enter the encounter metadata.

What’s weird about that one is that the annotation belongs to a different encounter, but if you click on it to view that encounter, it’s already been deleted. So now we just have a ghost annotation that can’t actually be matched or deleted from appearing here.

1 Like
4

Hi Anastasia,

Thank you for your recommendation. I have tried it out and manually added an annotation. I think it works and I can use this method when I come across encounters with the same problem. After trying to match, I received the “attempting to fetch results” message. I understand this will take more time to solve.

Yes the ghost annotation is weird as I have not noticed any repeated uploads of the encounters and it appears to affect random encounters after being uploaded.

Let me know if you would like any more examples.

Many thanks, Ruth

5

Thanks for the quick follow-up! There’s some odd behavior with ID jobs falsely returning a complete status without actually completing. We’ve been working on that today and hope to have an update soon as we see this in a handful of other encounters in Flukebook.

6

Sorry about the late update. I think this is actually related to a larger bug that we’re still working on fixing: Known Issues with Detection and Identification - March 23, 2026

7

Okay, thank you for the information.

8

Ok, this bug has been fixed. I re-ran all the matches from your linked encounters and they have match results now. The last two links you will need to view the latest match from the encounter page since the links you shared are just for that specific match attempt. Thanks for your patience!

9

Thank you Anastasia! Yes the matching is working well now :smiley:

1 Like
10

Hi Anastasia,

Sorry to be coming back to the same problem. I continue to have ghost annotations created now and then, but the solution you suggested previously is working.

However, just recently all of my matching attempts are coming back with “attempting to fetch results”. I include some links to a few;

Please could you help me understand what is going on here.

Many thanks,

Ruth

11

I see match results for all of the links you shared. If your uploads were recent, they just needed time to finish processing.

12

Okay, thank you for confirming that they have match results. As all the encounters came back with the same message, but had been uploaded for varying lengths of time, I assumed that maybe it was a bug. Perhaps this issue was due to my internet connection. Apologies for bothering you over a small thing, but thank you for your quick response. :sweat_smile:

13

No worries! It’s always the moment you ask someone to take a look that the problem suddenly resolves itself. :sweat_smile:

1 Like