# Activity position in waiting to import list

**URL:** https://community.citystrides.com/t/activity-position-in-waiting-to-import-list/19903
**Category:** Ideas
**Created:** [April 11, 2020, 4:01pm UTC](https://community.citystrides.com/t/activity-position-in-waiting-to-import-list/19903 "2020-04-11T16:01:36Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![JamesChevalier](https://community.citystrides.com/user_avatar/community.citystrides.com/jameschevalier/32/2_2.png) [@JamesChevalier](https://community.citystrides.com/u/JamesChevalier)
#### Post date: [April 11, 2020, 4:17pm UTC](https://community.citystrides.com/t/activity-position-in-waiting-to-import-list/19903/2 "2020-04-11T16:17:23Z")

</div>

Yeah, I need to improve/add to [How Syncing Works](https://community.citystrides.com/t/how-syncing-works/19443)

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.

---

_[View the full topic](https://community.citystrides.com/t/activity-position-in-waiting-to-import-list/19903)._