Start New Search error

[nathankota]

This seems to happen randomly, so I cannot reproduce it regularly; and I forgot to click on Show technical details 🤓 to see what information is there, but maybe this can be a placeholder issue for future errors.

After performing an advanced search, when I click Start New Search I sometimes get the error page:

[stdavis]

@nathankota I'm unable to reproduce this. I have made improvements to the logic related to the search wizard since this issue was opened. Perhaps it's fixed?

[nathankota]

• I did a statewide search of four point layers to test Add default opacity for point layers #574. One layer was Oil and Gas - Wells, which resulted in a Failed to fetch error.
• I navigated around the page, clicked on some points, then let the page sit for several minutes while I did some other things. One point was selected.
• When I came back to it and clicked Start New Search I got the error page.
• Clicking on Show technical details resulted in:

TypeError: Cannot read properties of null (reading 'indexOf')
at https://enviro.dev.utah.gov/assets/index-HfvjSQHl.js:4964:15389
at gO (https://enviro.dev.utah.gov/assets/index-HfvjSQHl.js:40:24328)
at h (https://enviro.dev.utah.gov/assets/index-HfvjSQHl.js:40:42530)
at jRe (https://enviro.dev.utah.gov/assets/index-HfvjSQHl.js:40:41350)
at Qm (https://enviro.dev.utah.gov/assets/index-HfvjSQHl.js:40:40387)
at sZ (https://enviro.dev.utah.gov/assets/index-HfvjSQHl.js:40:36975)
at vm (https://enviro.dev.utah.gov/assets/index-HfvjSQHl.js:38:3292)
at https://enviro.dev.utah.gov/assets/index-HfvjSQHl.js:40:34339_

The layers I queried at a statewide level were:

• Oil and Gas wells
• Brownfields Targeted
• UPDES Dischargers
• Solid Waste Facilities

[stdavis]

From Nathan:

I keep getting the Something went wrong error, again after letting it sit for a while after doing statewide Public Water System Facilities search.

A "while" means a few minutes.

[nathankota]

I've been doing a variety of searches this morning and using the Start New Search button frequently, both immediately after a search and after letting the app sit for 1-10 minutes, and have not come across the error.