Class: ReportScheduleService

Defined in: server/insights/scheduling/report-schedule-service.ts:138

The request-path orchestrator for scheduled deliveries. Its whole reason to exist is to keep TWO stores in lockstep: the saved_report_schedules row (the durable record) and the BullMQ job scheduler in Redis (what actually fires). Every write goes through here so the two never drift:

• create commits the desired row before registering the scheduler. If registration fails (a custom cron BullMQ rejects), the row is rolled back only when no newer mutation has superseded it.
• update rewrites the row, then re-registers the scheduler. If the new config can't register it ROLLS THE CONFIG BACK to the last-known-good one (the schedule keeps delivering on its old pattern) rather than pausing — never silently kill a healthy schedule on a bad edit or a Redis blip.
• setEnabled flips the row, then re-syncs: enabled → upsert; disabled → remove. Enabling a schedule whose config can't register fails closed (it stays disabled) — you can't enable a broken schedule.
• delete soft-deletes the row, then removes the scheduler.

The row is always committed FIRST (it is the source of truth). Redis calls never occupy a database transaction or make uncommitted state observable. Every mutation increments a durable version copied into BullMQ job data; stale writers re-read and apply the newer desired state, while stale fires skip delivery. Cross-store atomicity is impossible (Redis + PG), so reconcileReportSchedules also closes the crash window between the committed row and its Redis synchronization at worker startup.

ConstructorsCopy Anchor Link

ConstructorCopy Anchor Link

new ReportScheduleService(deps: ReportScheduleServiceDeps): ReportScheduleService;

Defined in: server/insights/scheduling/report-schedule-service.ts:141

ParametersCopy Anchor Link

ReturnsCopy Anchor Link

ReportScheduleService

MethodsCopy Anchor Link

create()Copy Anchor Link

create(input: CreateReportScheduleInput, ctx: ReportScheduleContext): Promise<ReportSchedule>;

Defined in: server/insights/scheduling/report-schedule-service.ts:200

ParametersCopy Anchor Link

ReturnsCopy Anchor Link

Promise<ReportSchedule>

createDashboard()Copy Anchor Link

createDashboard(input: CreateDashboardScheduleInput, ctx: ReportScheduleContext): Promise<DashboardSchedule>;

Defined in: server/insights/scheduling/report-schedule-service.ts:227

ParametersCopy Anchor Link

ReturnsCopy Anchor Link

Promise<DashboardSchedule>

delete()Copy Anchor Link

delete(id: string, ctx: ReportScheduleContext): Promise<void>;

Defined in: server/insights/scheduling/report-schedule-service.ts:534

ParametersCopy Anchor Link

ReturnsCopy Anchor Link

Promise<void>

get()Copy Anchor Link

get(id: string, ctx: ReportScheduleContext): Promise<ReportSchedule>;

Defined in: server/insights/scheduling/report-schedule-service.ts:180

ParametersCopy Anchor Link

ReturnsCopy Anchor Link

Promise<ReportSchedule>

getDashboardScheduleManagement()Copy Anchor Link

getDashboardScheduleManagement(dashboardKey: string, ctx: ReportScheduleContext): Promise<DashboardScheduleManagementState>;

Defined in: server/insights/scheduling/report-schedule-service.ts:254

ParametersCopy Anchor Link

ReturnsCopy Anchor Link

Promise<DashboardScheduleManagementState>

list()Copy Anchor Link

list(ctx: ReportScheduleContext, savedReportId?: string): Promise<ReportSchedule[]>;

Defined in: server/insights/scheduling/report-schedule-service.ts:148

ParametersCopy Anchor Link

ReturnsCopy Anchor Link

Promise<ReportSchedule[]>

listRuns()Copy Anchor Link

listRuns(id: string, ctx: ReportScheduleContext): Promise<InsightScheduleRunSummary[]>;

Defined in: server/insights/scheduling/report-schedule-service.ts:189

ParametersCopy Anchor Link

ReturnsCopy Anchor Link

Promise<InsightScheduleRunSummary[]>

runNow()Copy Anchor Link

runNow(input: RunReportScheduleNowInput, ctx: ReportScheduleContext): Promise<RunReportScheduleNowResult>;

Defined in: server/insights/scheduling/report-schedule-service.ts:563

Enqueue one delivery without changing recurring state. Disabled schedules may be run deliberately; deletion, tenant scoping, write authorization, corrupt config, and concurrent mutations all fail closed before send.

ParametersCopy Anchor Link

ReturnsCopy Anchor Link

Promise<RunReportScheduleNowResult>

setEnabled()Copy Anchor Link

setEnabled(
   id: string, 
   enabled: boolean, 
   ctx: ReportScheduleContext
): Promise<void>;

Defined in: server/insights/scheduling/report-schedule-service.ts:461

ParametersCopy Anchor Link

ReturnsCopy Anchor Link

Promise<void>

update()Copy Anchor Link

update(
   id: string, 
   input: UpdateReportScheduleInput, 
   ctx: ReportScheduleContext
): Promise<ReportSchedule>;

Defined in: server/insights/scheduling/report-schedule-service.ts:348

ParametersCopy Anchor Link

ReturnsCopy Anchor Link

Promise<ReportSchedule>

updateDashboard()Copy Anchor Link

updateDashboard(
   id: string, 
   input: UpdateReportScheduleInput, 
   ctx: ReportScheduleContext
): Promise<DashboardSchedule>;

Defined in: server/insights/scheduling/report-schedule-service.ts:372

ParametersCopy Anchor Link

ReturnsCopy Anchor Link

Promise<DashboardSchedule>