Yeah, I need to improve/add to How Syncing Works
There is no “place in the queue” or a static order of things. I have X number of activities that all want to be synchronized, and any/all subscriber activities have priority before any non-subscriber activities are synchronized. When the Strava API limit is reached, any lingering activities to be synced are scheduled out after the next reset (be it a 15min or 24hr limit reach).
The fact that these jobs are attempted, then potentially rescheduled (limit reached) means that there’s no visibility into how long a job has been in this whole system - each attempt/retry/requeue/reschedule is a new instance.
One change that I intend to add is to have historic/full-account Strava syncing go into a lower priority queue so that new activities can make their way into CityStrides and the history-filling won’t block that. This means that new users have a degraded experience, but it’s basically my only option at this point.