Yeah, this looks caused by an incorrect node count stored on the street. Given the last sync date of the city, I think it ran against the old code … I’m more confident that the new code doesn’t leave incorrect counts sitting around afterwards, so I’m going to send the city in for a sync to see if that resolves everything.
The city sync has caused the node count to match the data on the map — perfect! There was one node actually added due to the sync that I haven’t yet visited. I picked it up today during the walk and was able to finish the city! 
Thanks for the help! I guess this is a good confidence check for the new sync process! 
I might be suffering from the same issue. (former subscriber fwiw)
I had 100% completion on Ann Arbor, but knew there were some streets in a new development I’d need to check off. Imagine my surprise on checking my status when I saw dozens and dozens of streets marked as incomplete. It looks like someone updated OSM and added nodes, in some cases refining curves or adding nodes in the middle of a stretch. These first two screenshots are from Nixon Road - I’ve run the entire length (parts of it on both sides) but these red nodes are showing up between purple ones. Second image zooms in on a short stretch. Third pic is a street I’d completed; used to have 5 nodes now has 7, I don’t have credit for 2 so drop below 80% even though those 2 are almost on top of credited nodes. These are the kinds of things I’m encountering.
For streets that I know I’d run multiple times I just marked them manually complete - but then wondered if that was not wise. So I’m tagging on to this thread. It looks like Ann Arbor was last updated in February (2026-02-03) but I don’t know if that’s in OSM or here in CS. Please advise as to what’s the best way to deal with this. Many of the streets are isolated and scattered about town, so returning to them to run one or two blocks feels inefficient yet leaving them incomplete grates on my completist nature… (FWIW today I figured I might as well revisit some streets closer to home as a way to plan my route, and they still don’t show as complete but that’s probably a case of “check again in 24 hours”. )
Okay, I don’t know how or why, but all those wacky streets have now been fixed. So thank you to whomever or whatever did it! (There are still 4 streets that are not publicly accessible (a test track on UMich campus); maybe I’ll finally learn how to update OSM to account for that.)
I believe I have a similar issue. This street shows 100% complete but not counting towards being finished:
136th Street Southeast - CityStrides
