Fix sync_lookback_days actually controlling the sync window
Build and push images / validate (push) Successful in 2s
Build and push images / build-backend (push) Successful in 48s
Build and push images / build-worker (push) Successful in 52s
Build and push images / build-frontend (push) Successful in 29s

Activities: lookback_days was ignored once last_sync_at was set (since
always took priority). Now lookback_days always sets the window; -1 is
all-time on first sync then incremental.

Wellness: lookback_days was never passed to sync_wellness at all —
hardcoded 90-day cap regardless of settings. Fixed by adding lookback_days
param and wiring it through from the Celery task.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
2026-06-07 01:34:18 +01:00
parent 22b41109f5
commit 211f77a574
2 changed files with 21 additions and 12 deletions
+4 -1
View File
@@ -507,7 +507,10 @@ def sync_garmin_connect_user(user_id: int):
if cfg.sync_wellness:
try:
wellness_days = sync_wellness(garmin, user_id, cfg.last_sync_at, db)
wellness_days = sync_wellness(
garmin, user_id, cfg.last_sync_at, db,
lookback_days=cfg.sync_lookback_days if cfg.sync_lookback_days is not None else 90,
)
except Exception as exc:
errors.append(f"wellness: {exc}")