Cache & Data Management¶
Stridevox caches your Garmin data locally for fast access. This page explains how caching works and how to manage your data.
How Caching Works¶
When you sync with Garmin, Stridevox downloads your fitness data and stores it in a local database. This means:
- Fast access — The AI and dashboard read from the local cache, not Garmin's servers
- Offline browsing — View your data even when Garmin's API is slow or unavailable
- Reduced API calls — Garmin has rate limits; caching minimizes how often we need to call their API
Cache Settings¶
Configure how much data to cache in Settings > Garmin Connect:
Activity Limit¶
- Default: 100 activities
- Maximum: 10,000 activities
- Controls how many activities are stored locally
- Use Check Total Activities in Garmin to see how many you have
Days Range¶
- Default: 30 days
- Maximum: 365 days
- Controls how many days of daily summaries and sleep data to keep
- Older data is not deleted — this only affects new syncs
Sync Operations¶
Incremental Sync (Fast)¶
Click Sync Data (Fast) to fetch only new data since the last sync:
- Checks for new activities
- Updates daily summaries for recent days
- Fetches any missing sleep data
- Fastest option for regular updates
Full Refresh¶
Click Full Refresh to clear the cache and re-download everything:
- Deletes all cached data first
- Re-fetches activities up to your Activity Limit
- Re-fetches daily summaries for your Days Range
- Takes longer but ensures data integrity
Clear Cache¶
Click Clear Cache to delete all cached data without re-fetching:
- Removes all activities, sleep data, and daily summaries
- The AI Chat will have no fitness context until you sync again
- Does not affect your chat history or settings
Background Jobs¶
For large syncs, use background jobs so the page stays responsive:
- Queue Full Refresh — Runs a full refresh in the background
- Queue Incremental — Runs an incremental sync in the background
Monitoring Jobs¶
The Background Jobs section shows:
| Status | Meaning |
|---|---|
| Pending | Job is queued and waiting to start |
| Running | Job is actively syncing data (shows progress %) |
| Completed | Job finished successfully |
| Failed | Job encountered an error |
Job Actions¶
- Refresh — Update the job list to see current status
- Cancel — Stop a running or pending job
- Retry — Re-run a failed job
Cache Status¶
The Data Management section shows what's currently cached:
- Activities: Number of cached activities
- Sleep data: Amount of sleep records stored
- Daily summaries: Number of daily summary records
- Last sync: When the cache was last updated
Best Practices¶
Recommended cache strategy
- Initial setup: Set Activity Limit to your desired history depth, then use Queue Full Refresh
- Regular updates: Use Sync Data (Fast) after each workout syncs to Garmin
- Weekly maintenance: No action needed — incremental sync handles everything
- Troubleshooting: If data seems wrong, use Full Refresh to rebuild the cache
Garmin rate limits
Garmin enforces API rate limits. If you get rate-limited, wait 2–3 minutes before trying again. Background jobs handle retries automatically.