Sydney ( Mel Cox is running Sydney, New South Wales - CityStrides ) was last sync’ed on 11/11/25 and created many red nodes for me which should not be red. (I referenced this in this thread: City was updated, suddenly some streets are showing as not completed). It has not been sync’ed since and I still have all the red nodes.
My question is, can Sydney be scheduled for a sync, or is it too big and would gum up the works for everything?
It can be bumped up in the queue, yeah. That’s a Supporter Feature & the entry is in the menu on each city page.
I’ve improved city sync speed a bit lately, so the largest cities in the world should finish within a week or so. Since Sydney hasn’t been updated in a while (and specifically within this time range), there will probably be more changes than usual to process… so we’ll see how close to the 1 week estimate this gets…
Thanks Jim. I wasn’t game to request a sync in case I broke the system, but I’ve just done so, so we’ll see what happens!
Down to 8 months now, just 2 hours later 
It’s an extraordinarily imperfect estimate 
I had to choose something other dividing by zero 
So the estimate can change during the sync, depending on which streets are being processed … a batch of small streets in an unpopulated area will fly by, estimating a quick time to finish … a batch of large streets in a populate area could take a long time, estimating a long time to finish.
I’m going to monitor this for a couple days. It’s not super useful to monitor on the scale of hours, especially when - like now - some streets being processed are going on 4, 5, 9 hours.
Is the city sync stuck? I’ve noticed the list on the status page hasn’t changed in at least 12 hours. Just wondering because I added Redondo Beach to the queue three days ago and it’s still in the queue.
It’s not stuck, it’s going to take a long time to finish.
Sydney has been going on for four days now, maybe done in a week? Then the queue can continue
I’ve seen well over a week for some to get updated. It’s no big deal, at least we have some control over the updates now, when we need it, just not necessarily immediately.
Sydney sync has now been going for 15 days. Any concerns that it might be stuck or could this still be normal?
Nope, it’s “working” as expected.
It’s finished! 19 days of hard slog. Would it be beneficial to sync Sydney more frequently, so that there isn’t such an accumulation of updates to process, or is it going to take that long regardless?
Big cities are limited to one update per month so I don’t think so. From how I understand it, the delay in processing a city update is more related to the number of striders and streets than to the actual changes to be implemented.
