Shark grid not right

Bug report template

In which Wildbook did the issue occur? Spot A Shark USA/shark grid

What operating system were you using? (eg. MacOS 10.15.3) Windows 7

What web browser were you using? (eg. Chrome 79) chrome

What is your role on the site? (admin, researcher, etc) admin

What happened? i sent several sharks to the grid, but one last night and one this morning (might have been the same encounter?) do not appear to be processing. there is no list in the grid of my pending (or completed) scan tasks. there should be 1 or 2.

981a237b-7641-4f3b-9f57-df3a67213e59 is the ID for the one I did this morning. It is possible that I randomly picked the same shark to try again this morning. Neither spot map appears in the encoutner page though for me to delete and start over, which has worked in the past.

I moved onto another shark today and it mapped and processed perfectly.

What did you expect to happen? normal scanning

What are some steps we could take to reproduce the issue? i got nothin!

Hi Carol,

Is there any chance you and Ara McClanahan could have been trying to perform the same task at the same time?

I definitely see a successful matching result for Ara:

and in the “View Audit Trail” section of the Encounter:

I see both of you making changes on the same day. This might be an example of:

  1. Ara mapped the spots and ran the scan, generating the result link above.
  2. You repeated the same process, but Wildbook only supports one left-side pattern and one right-side pattern per Encounter, so Ara’s result would have been what you should have been directed too, though you won’t see it by default because the sharkGrid be default makes a sublist of only your submitted tasks. Clicking “Show All Tasks” on the Grid Administration page ( would reveal Ara’s match, which would need to be deleted before a new scan of the pattern could be run.

Since you’re seeing what you expect today, this might be an example of two people working on the same data roughly simultaneously.

Does that sound reasonable, or were there other things that seemed weird?