Scheduler adapter
A one-way receive-side adapter whose sole job is to fire on a repeating interval and publish a triggering message. The platform's single source of timing.
The Scheduler is unusual in that it does not talk to anything outside the bus. No connection, no credentials, no external payload — only a tick.
The cadence is set by two fields: a numeric Repeat Every value and a Repeat Unit picker. Every recurrence in the system is expressed this way.
Optional. Turn on Start Date Window, End Date Window, or both to confine the schedule to a calendar range. Before the start date the Scheduler is silent; after the end date it stops permanently.
Optional. Turn on Daily Window and set Daily Start Window and Daily End Window (clock times) to keep ticks inside a specific part of each day. Outside the window the Scheduler is silent on that day; the next day it begins firing again at the start time.
Configured on the receive port the Scheduler is bound to, under the ScheduledListenerConfig panel.
Repeat Every — required; numeric value. How many units pass between consecutive ticks.
Repeat Unit — required; dropdown (Minutes, Hours, Days, etc.). The unit Repeat Every is measured in.
Start Date Window — optional toggle + date picker. When on, the schedule is silent before this date.
End Date Window — optional toggle + date picker. When on, the schedule stops after this date.
Daily Window — optional toggle. When on, exposes Daily Start Window and Daily End Window.
Daily Start Window — clock time (HH:mm:ss aa). The earliest time of day a tick will fire.
Daily End Window — clock time (HH:mm:ss aa). After this time of day, ticks stop until the next day.
Payload — optional; the body of the firing message. Leave empty for an empty body; the tick still carries the standard message envelope and can be subscribed to on Message Type alone.
The Scheduler is the only shipping adapter with no Authentication. There is no external endpoint to reach and no credentials to manage; the picker on the receive port is disabled when this adapter is selected.
If credentials are needed somewhere in a Scheduler-triggered flow, they belong on the downstream send port, not here.
That is the Scheduler
One-way receive, no Authentication, one place for every timer in the system. Back to Adapters.