Feedback hevy sync cadence

---

name: Hevy sync: nightly cron + on-demand, not hourly description: Justin rejected hourly polling for Hevy; nightly cron + /sync-workouts bot command is the right shape type: feedback

---

Hevy sync should run nightly (~23:30 CT) + on-demand bot command, not hourly.

Why: Justin does ~3 workouts per week. 168 polls/week to capture 3 events is wasteful even when free. The wellness daily aggregator only consolidates once per day anyway, so hourly granularity has no downstream consumer.

How to apply: When building or modifying the Hevy poller, default to a single nightly cron using /v1/workouts/events?since=<last_sync> for incremental pulls. Pair it with a /sync-workouts bot command for immediate post-workout pushes. Do not propose hourly polling for any fitness data source unless Justin has a real-time dashboard need.

[Claude Code]

[auto-memory session 3cdcd248-1632-4c02-bba4-6e3b8ea3aa02, confidence 0.85, mode direct]