Updates / Piston Server

Recurring Recording Schedules

· Build 895

Recurring Schedules (new)

  • Record on a schedule without an operator — "every Tuesday and Thursday 18:30 for two hours". On the New Session page, set Repeat to Every day or Weekly, pick a time of day, duration and weekdays, and save; everything else on the form (cameras, markup, options, scoreboard, sharing, S3) becomes the template each recording is made from
  • Optional Starts from and Ends on dates — set up next season's training now, or give a schedule a last day; it pauses itself after its final run and shows a checkered-flag Finished pill rather than a failure
  • A RECURRING SCHEDULES panel on the Sessions page shows each schedule's summary, a live countdown to its next run, and how the last run went (a green pill that opens the recorded session, or a red one whose tooltip explains a failure — cameras busy, box was off). Pause/resume, skip just the next run, duplicate (created paused so it can't double-fire), edit or delete from the row
  • Each recording is named after the schedule with the date ("Tuesday Training — 18 Aug 2026") and stops on time even if it starts a little late; a run the box slept through is recorded as missed rather than started as a stub
  • Available to the Control Centre and other integrations via /api/session_schedules (list, create, update, pause/resume, skip, duplicate, delete)

Sessions

  • [object Object]