How Syncing Works

General Notes

  • your full history will be synchronized into CityStrides, there is no limit to the number of activities that will sync … except for limits imposed by tracking services like Garmin and Coros
  • running, walking, and hiking activity types are allowed in
  • there are usage limits in each service that may cause sync delays
  • the Status Page shows some detail on delays
  • an activity must first be synchronized into CityStrides, and then it can be processed for completed/progressed streets
  • post-sync activity processing has its own queues (which can be delayed; see Status Page Wiki)
  • most services provide webhooks, so CityStrides is alerted of each activity after it is saved there
  • Runkeeper does not have webhooks, so each account is synced once per day (Supporters get can request a sync at any time)

Activity Processing Prioritization

This is how the system weights the different queues. It works through a queue in its entirety before moving onto the next queue. This is all specifically for street progress/completion.

  • Subscribers
  • New users
  • Regular users
4 Likes