CityStrides has a status page. Hopefully this will help you make some sense of it!
Section 1: Strava Sync
Strava limits how many times Citystrides can access its data by the 1/4 hour and by the day. This section tells you the current information and gives you a sense if there might be a delay in your Strava Activity getting brought into CS. If your account doesn’t seem to be updating, but there are “activities scheduled for import” that is probably the reason.
Those who support the site get priority in Strava import of new activities.
Strave queue priority:
- Subscriber new activities
- Regular new activities
- Subscriber historic activities
- Regular historic activities
Section 2: MapMyFitness Sync
Similar situation as to Strava, but a lot fewer Striders use it to get their activities into CS, so it is usually in better shape with regards to the limits.
Section 3: Runkeeper Sync
Unlike Strava and MapMyFitness, every Runkeeper sync is a full-account sync, so this section is set up to show how many accounts are currently scheduled for import from Runkeeper
Section 4: Activity Processing Delay
Once your activity is synchronized with your data source (Strava, MapMyFitness, etc) the Citystrides server needs to take that data and calculate the progress you achieved during that activity and show it on your account. Site supporters get improved priority when it comes to this step in the process.
While waiting for this processing to complete, you may experience a situation where an activity shows on your profile, but either shows no completed/progresses streets or shows progressed streets but no completed streets. In most cases, more time is all that is required for this to continue to process before it is done.
Section 4: LifeMap Generation Display
Did you know supporters of the site get an advanced LifeMap? Benefits include faster loading, map filtering, the “Node Hunter” function, activity track identification and more. This section indicates the delay in the Citystrides servers initiating an update of that LifeMap once an activity has been synchronized to your account. Actual processing time of this map varies depending on server load and account activity count, so there may be an additional delay between synchronization and the map processing being completed.