I did a resync of Elmbridge and seem to have lost this street Beales Lane - CityStrides that held since 2020! Sure I have been “given” whole (short) streets have not even run down before but this tolerance seems a bit “harsh” ?
It’s been 25 meters since I started in 2013.
Can you share the activity link? I’ll try to take a closer look…
CityStrides and on OSM Way: Beales Lane (147177640) | OpenStreetMap has not changed since 2018 it seems
Elmbridge was the first city I did as that is where I live so would not left odd nodes about as first completed back in 2020. The resync pulled in a gated short road I changed in OSM to make the bit behind the gate. Ironically I tried to run it today and got “near enough” to be given it anyway. I was going to go down to Beales Lane and not cut the corner by a few metres this time but something odd is happening as I surely “got” this road at the time.
Ah the node in question at the intersection has been changed recently
https://www.openstreetmap.org/node/1628132966/history
some synch issue ?
Further oddity here is Beales Lane seemingly does not go to the end of the road as turns into Church Walk. On Street View I can see a Church Walk street sign where it starts. That should not effect this as OSM has Beales Lane for the full length and whatever road it is in, I surely got “near enough” ?
I have reworked this intersection and street name as per above so will see what happens when try a resync in a few days
This is weird - I supposedly completed Church Walk CityStrides couple of months later without actually going there that day unless this is a rogue node. But right now Church Walk shares a node with Beales Lane I ran “near” above CityStrides
Yeah, this activity is within 25m of that node. The query that runs after creating/updating a street isn’t picking up this activity for some reason … looking into it now …
Am literally about to run it again so will see if that works. I did slightly change it so one node is possibly borderline 25m anyway, not tried a re sync yet though…
I just released the fix for this … it looks like it probably only affected situations where a single node was moved.
If you want the completion date to be correct, you can mark it as manually complete and then unmark it. That’ll force it to figure things out again.
Thanks ! Just ran and got it this time so back to 100% on my first completed one (must have done that 10 times or so) but being pedantic wanted to run the tiny extra bit I added anyway 
PS same problem on Park Lane - CityStrides - I tried marking as manually done then undid that. Not sure if it has worked or maybe still processing.
Mismatch now of counts. i am off to do run the two I “really” have not yet run…
Yeah, that work goes to the same queue that city syncing uses & it’s still working through a large backlog. I’m hopeful that it’ll go through today.