nodes/generated

Interface ScheduleTriggerNodeParameters

Source


interface ScheduleTriggerNodeParameters {
    misfireGraceSeconds?: number;
    misfirePolicy?: "skip" | "coalesce" | "coalesce_owner";
    rule?: {
        interval: {
            daysInterval?: number;
            expression?: string;
            field?:
                | "minutes"
                | "hours"
                | "days"
                | "weeks"
                | "months"
                | "seconds"
                | "cronExpression";
            hoursInterval?: number;
            minutesInterval?: number;
            monthsInterval?: number;
            notice?: string;
            secondsInterval?: number;
            triggerAtDay?: (0 | 1 | 2 | 3 | 4 | 5 | 6)[];
            triggerAtDayOfMonth?: number;
            triggerAtHour?:
                | 0
                | 1
                | 3
                | 2
                | 4
                | 5
                | 10
                | 15
                | 6
                | 7
                | 8
                | 17
                | 16
                | 13
                | 9
                | 11
                | 19
                | 20
                | 21
                | 12
                | 14
                | 22
                | 23
                | 18;
            triggerAtMinute?: number;
            weeksInterval?: number;
        }[];
    };
    skipDurableScheduler?: boolean;
}

Properties§

§readonly misfireGraceSeconds?: number

How late an execution may start before it counts as missed. Set to 0 to use the instance setting. Type options: {"minValue":0,"numberPrecision":0}

§readonly misfirePolicy?: "skip" | "coalesce" | "coalesce_owner"

Default: "skip"

§readonly rule?: { ... }

Default: {"interval":[{"field":"days"}]} Type options: {"multipleValues":true}

§readonly skipDurableScheduler?: boolean

Whether to run this trigger through the legacy in-memory scheduler instead of the durable scheduler