Spot map results page displays cached spot maps

[goddesswarship]

Expected behavior

1. From the Encounter page, click the Remove spots button to reset a spot map
2. Create a new spot map
3. Click the Review scanTask results button
4. The match page will show the results based on the newest spot map

Current behavior

1. From the Encounter page, click the Remove spots button to reset a spot map
2. Create a new spot map
3. Click the Review scanTask results button
4. The match page only shows the results of the old spot map, no matter how many times a new spot map is cleared and re-created.

Example: Encounter link

Investigation notes
Even though the Encounter page (src/main/webapp/encounters/encounter.jsp) shows that 12 spots were mapped and sent to scanTask, the Modified Groth and I3S results (src/main/webapp/encounters/scanEndApplet.jsp) display the cached map and results from last year.

This is the bottom of the Encounter page. This shows the 12 spots from the newest spot map reflecting on the page:

This image of the Groth scan results page, shows the date of the scan as November 2023, even though the latest spot map was submitted for scanning in March 2024.

The I3S tab of the scan page also shows the most recent scan as Nov 2023.

Additional example: This spot map was made on March 11, but it's still showing the cached scan from Feb 14
https://www.sharkbook.ai/encounters/scanEndApplet.jsp?writeThis=true&number=a263becc-c2d3-4066-be5c-4520a8c16a40&taskID=scanRa263becc-c2d3-4066-be5c-4520a8c16a40&rightSide=true

Community link
https://community.wildme.org/t/sharkbook-cannot-reset-spots/2823
https://community.wildme.org/t/what-does-unable-to-fetch-data-200-mean-s/2833/2