Timers give you control over how your flows behave over time.
Changelog
12 versions
v1.5.3Latest
Scheduler (appmixer.utils.timers.SchedulerTrigger): fixed the `Days of Month` schedule firing only on the earliest selected day. Every selected day now fires, and `last day of the month` can be combined with numeric days.
Scheduler (appmixer.utils.timers.SchedulerTrigger): a `Days of Month` value outside the offered range (e.g. `31`, set through the API or an imported flow) now fails with a clear error instead of silently overflowing into the next month.
v1.5.2
Scheduler and Cron Scheduler: fixed "Cannot read properties of undefined (reading 'timeoutId')" when the trigger is started with state saved by an earlier run, e.g. while publishing a draft over a running flow.
v1.5.1
Security: upgraded moment to 2.31.0 (medium advisory).
v1.5.0
Added test() (Flow Test Mode) to triggers (Scheduler, SchedulerTrigger, Timer).
v1.4.0
SchedulerTrigger: added test() (Flow Test Mode) — emits one well-formed schedule payload via the same getNextRun() computation, without setting timeouts or touching state.
v1.3.0
Implemented multiselect input normalization for SchedulerTrigger daysOfWeek and daysOfMonth fields.
Schedule jobs to run periodically based on various time intervals, such as daily, weekly, monthly, or custom intervals. It supports advanced configurations like start and end times, time zones, and immediate triggering.
This trigger fires at the frequency provided by the interval configuration property. First message is sent to output when flow is started, this message does not have 'lastTick' and 'elapsed' property set.