@cfxlabsinc/b2b-services
    Preparing search index...

    Cadence input accepted when creating or editing a schedule. Uses Temporal's authoring types (CalendarSpec accepts loose ranges like { hour: 17 }; IntervalSpec.every accepts ms or an ms-formatted string), so the form builds a spec Temporal can consume without a translation layer here.

    type TemporalScheduleSpecInput = {
        calendars?: CalendarSpec[];
        cronExpressions?: string[];
        intervals?: IntervalSpec[];
        timezone?: string;
    }
    Index
    calendars?: CalendarSpec[]

    Provide exactly one of calendars / intervals / cronExpressions.

    cronExpressions?: string[]
    intervals?: IntervalSpec[]
    timezone?: string

    IANA timezone the calendar/cron times are interpreted in. Optional because a real schedule can genuinely carry none: Temporal maps an absent timezone to an empty timezoneName on the wire and interprets the times as UTC, and some of the schedules the dashboard masters were registered that way. An explicit undefined here is byte-identical to omitting the field, so "preserve the absence" is expressible rather than being silently pinned.