Hello,
When clicking the three dots above last synced map I only get a blank box.
Have tried different citys, different browsers, hard resetting my browser. No change.
It disappeared in the last 10 days I belive
1 Like
As @JamesChevalier said in other topics:
The city sync feature is currently disabled due to a full rework Iām testing now. I only āquietlyā announced this in Water Station because itās not a widely used feature & the testing is going to run a while.
1 Like
Seems like one of those features that many users donāt use, but the minority of us that do use it are checking twice a day to see when itās back 
5 Likes
Lol, yep. 100% of the reason for becoming a subscriber last week and then it goes away 
Well donāt give up yet - itās not like he took it away just to frustrate us! The reason itās missing is that James is rewriting the code for city updates to be more efficient and frequent, so this is a temporary hindrance to make the site better as a whole.
@kevincharlespels Haha, I know. Luckily, I did get most of my updates done before it shut off. What he does that IS frustrating is not queueing activity deletes at a low priority instead of rejecting them for hours at a time. Ever since you mentioned RunKeeper, Iāve been attempting cleanup but that is also being affected.
1 Like
Hmm that could be an interesting idea - create a separate queue(s) for deleting activities and/or city updates that runs at lower priority, rather than simply rejecting and saying ātry again laterā. If you formally proposed it as an idea, Iād vote for it!
Perhaps it could be a supporter-only feature to encourage signups and not create too huge a queue. Non-paying users need to try again later, paying users get to enter the queue, and when the processing load abates, the supporters requests are prioritized.
Iāve definitely thought about it, but since I wasnāt attempting deletes before this current testing, I wasnāt sure if it was also just a side effect and when Jamesā current project is over, waits would become reasonable. What have people seen historically on how often the rejects occur?
Mostly itās just variable, depending on extenuating factors like an AWS outage or a really large city update clogging up the processing load - the latter being one impetus for the current city update overhaul.
1 Like
Oh, that reminds meā¦ During this city sync rework, I also adjusted how activity deletion post-processing occurs. I should be able to rework that rejection as well. Outside of Nodevember (which has become its own beast as years go by & more people join CityStrides), that should probably reduce rejections to near-zero.
The rationale behind rejection vs low priority / super delayed queueing is that I donāt have a status display of the queuing, so there would always be a question of whether the activity was still queued etc etc etc ā¦ which would likely lead to more support emails, which I already barely keep up with
I think youāre right about there being a better way of handling the situation, itās just that I donāt always have the time to work through the best implementations - sometimes I need to go with the least worst and then circle back.
4 Likes