Skip to content
iQBus HomeDocumentationBlogContact
Updated September 7, 2026
Adapters/Scheduler adapter
Adapter

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.

ADAPTER · RECEIVE Scheduler Fires on a repeating interval and publishes a triggering message Shipping DIRECTION ↓ Receive MODES One-way only AUTHENTICATION ✗ None PORT Receive port

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.

RECEIVE PORT Scheduler No Authentication on tick Bus tick message SEND PORT any subscriber to the tick SEND PORT any subscriber to the tick SEND PORT any subscriber to the tick One schedule, any number of downstream consumers. Timing lives in one place.

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.

EVERY 30 SECONDS tight cadence for near-real-time pickups EVERY 1 MINUTE the typical polling-replacement cadence EVERY 4 HOURS batch-style cadence for digests and rollups
i
The Repeat Unit picker covers the usual set, Seconds, Minutes, Hours, Days, etc. Time Zone is set on the same screen because the two windows below are clock-aware; the cadence itself is interval-based.

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.

CALENDAR · START DATE WINDOW 2026-06-01 · END DATE WINDOW 2026-06-21 before start, silent schedule active ticks fire on the configured cadence after end, stopped May Jun 1 Jun 21 Jul Either bound is independently optional. Leave both off for an open-ended schedule. Useful for time-limited campaigns, post-go-live one-offs, or staged cut-overs.

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.

24-HOUR DAY · DAILY START 08:00 · DAILY END 20:00 silent tick fires, active silent 00 08 12 20 24 Clock times are interpreted in the configured Time Zone, not UTC. Stack Date Window and Daily Window for both gates, ticks fire only where both are open.

There is no "fire at 06:00" setting, and the reason is worth stating plainly. The cadence is an interval counted from the moment the port is enabled, so Repeat Every 1 with Repeat Unit Days does fire once a day, but at whatever time of day the port happened to be started, and it moves again every time the port is restarted. The Daily Window schedules nothing either; it only suppresses the ticks that fall outside it. A daily job at a chosen time comes from combining the two: run a short interval around the clock, and open the window for exactly one interval’s width.

Daily End Window = Daily Start Window + Repeat Every, one second less. A window as wide as the interval cannot hold two ticks that are one interval apart, and it cannot hold none, because the ticks never stop. So exactly one tick lands inside it each day, whatever time the port was enabled and however often it is restarted. Outside the window the port only wakes, checks the clock, and goes back to sleep.

For a job that runs each morning at six: Repeat Every 5, Repeat Unit Minutes, Daily Window on, Daily Start Window 06:00:00 AM, Daily End Window 06:04:59 AM. Tighten the arrival by shortening both together, 1 Minutes with 06:00:00 AM to 06:00:59 AM, or loosen it the same way, 1 Hours with 06:00:00 AM to 06:59:59 AM. The Time Zone is what makes those clock times mean local time.

i
Both ways of mismatching the two have a cost. A window wider than the interval holds more than one tick, so the job runs twice in the same day. A window narrower than the interval can fall between two ticks and hold none, so a day passes with the job never running at all. Match them and neither can happen. The daily sales report tutorial builds a scheduled job on this rule.

Configured on the receive port the Scheduler is bound to, under the ScheduledListenerConfig panel.

Time Zone, required; dropdown. Used to interpret the Date Window and Daily Window clock times. The cadence itself (Repeat Every) is interval-based and time-zone-agnostic.
Repeat Every, required; numeric value. How many units pass between consecutive ticks.
Repeat Unit, required; dropdown (Seconds, 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.
i
Direction and mode are not configurable. The Scheduler is one-way receive by construction, there is no external caller waiting for a response, so two-way mode is not offered on receive ports bound to this adapter.

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.