You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since the schedule surfaces were removed (#160/#180), the Sources page no longer shows when the next sync will happen, and there's no way to control it. Restore both: surface the next scheduled check per feed, and let the user set the daily check time.
Desired behaviour
One global daily check time for all feeds (a single HH:MM, local). TWIC and Lichess Broadcasts are both checked daily (TWIC's real cadence is weekly, Lichess's is monthly — a daily check just fetches new data as soon as it lands).
Catch-up if missed: if the machine was off at the scheduled time, the check runs at the earliest possible moment after it (the scheduler already models this via last_run < most_recent_scheduled).
Visibility: each enabled feed shows its last sync and the next scheduled check ("next check ~04:00, in 3h") on the Sources page.
Configurable from the Sources page (editable time control).
Notes / where
The scheduler still has schedule.daily_minute + most_recent_scheduled + feeds_due_for_resync (scheduler.rs) — the mechanism exists; this is mostly re-exposing it. The GET/PUT /schedule endpoints were pruned in Prune orphaned schedule endpoints + run-now path (dead after #160) #180 and would need re-adding (a minimal get/set for the daily time).
Ajedrez is a one-time bulk source and must NOT appear here as a recurring schedule (see the Ajedrez ticket).
Related
#160 (unified update schedule — removed the global toggle), #180 (pruned schedule endpoints), scheduler.rs.
Summary
Since the schedule surfaces were removed (#160/#180), the Sources page no longer shows when the next sync will happen, and there's no way to control it. Restore both: surface the next scheduled check per feed, and let the user set the daily check time.
Desired behaviour
HH:MM, local). TWIC and Lichess Broadcasts are both checked daily (TWIC's real cadence is weekly, Lichess's is monthly — a daily check just fetches new data as soon as it lands).last_run < most_recent_scheduled).Notes / where
schedule.daily_minute+most_recent_scheduled+feeds_due_for_resync(scheduler.rs) — the mechanism exists; this is mostly re-exposing it. The GET/PUT/scheduleendpoints were pruned in Prune orphaned schedule endpoints + run-now path (dead after #160) #180 and would need re-adding (a minimal get/set for the daily time).Related
#160 (unified update schedule — removed the global toggle), #180 (pruned schedule endpoints), scheduler.rs.