This must be related to the changes in Updates on September 15, 2022 (Release 621)
The fact that showing/hiding streets works is a bit confusing, because a large part of the underlying changes were in that area.
I have monitoring in place, and it’s showing some of these Node Hunter requests are taking minutes 
with none of them taking over 2min.
- Thanks for the comment noting that the nodes do eventually appear, that’s helpful
- I’m also interested in which city you’re having this issue (a link to one or two may help, even if it’s every city in your experience)
Can you clarify whether the slowness you experienced was before or after that Sept 15 release?
No, it’s definitely not expected behavior & I’ll be working to fix it. The reason I’m working on this at all is from Show incomplete streets - #11 by ward_muylaert and some conversation above that post, where people were experiencing minute+ waits when using Node Hunter.
Thanks for sharing the console error. Basically, it looks like the previous version was taking a long time (about a minute) and this newly released version is taking even longer (status of 524 is a timeout).
I just updated the code to revert some of my recent changes. I’m interested in whether this improves things… Ideally:
- Close the current tab you have CityStrides open in
- Open a new tab and navigate to your city page
- At any zoom level, click Node Hunter
- Wait for nodes to appear, generally noting the time it takes (doesn’t need to be accurate)
- Click the X to hide the nodes
- Zoom/pan to a different section of the map & click Node Hunter
- Wait for nodes to appear, generally noting the time it takes (doesn’t need to be accurate)
I’m looking to see if it’s overall faster, and whether the second request is even faster still.