Scheduled reports
The /schedules web route currently renders fixed example schedules. Preview and menu interactions operate on those constants and do not call Reporting API. Creating, pausing, editing, deleting, or running a schedule from this screen is not a persisted workflow.
Reporting API separately provides live /report-schedules CRUD and POST /report-schedules/:scheduleID/run. Schedule records store cron expression, timezone, output format, and structured config. Plan limits cap schedule count.
The scheduler accepts the supported cron forms defined by the backend and computes due runs server-side. Delivery state is recorded with the report run; the fixture web page does not expose the actual recipient config or delivery worker state.
Use the API reference for programmatic schedule management until this route is connected.