Routing node - Business Hours

Introduction

The Business Hours node routes messages based on time-of-day and day-of-week schedules. Each configured rule produces a separate output port. Add one or more Schedule rules to define the days and time window for that output. An optional Otherwise rule acts as a catch-all fallback for when no schedule rule matches.

Configuration

Setting	Description
Timezone	Determines which timezone is used when evaluating the schedule rules. By default UTC is used when left empty. Start typing to filter available timezones via autocomplete, or click the dropdown button to browse all available timezones.
Time	The reference time used for evaluating rules. By default the message timestamp is used (Message timestamp). You can also select a time value from a message property or from flow/global context.
Business Hours	The list of rules for this node. Each rule can be one of the following types: Schedule — Select one or more days of the week and a start/end time window. Each schedule rule generates a corresponding output port on the node. Otherwise — A catch-all fallback rule. The message is routed here only when no schedule rule matched. Rules are evaluated from top to bottom. Use the drag handles to reorder them.
Stop on first match	When enabled, only the first matching rule produces output and evaluation stops. When disabled, the message is forwarded to every rule that matches, potentially producing output on multiple ports simultaneously.

Validation

Each Schedule rule must have at least one day of the week selected, and the end time must be strictly after the start time. Invalid rules are highlighted in the editor and will block deployment until corrected. Overnight time spans (e.g. 22:00–02:00) are not supported; use two separate rules instead.

Output

The incoming message is forwarded unchanged to the matching output port(s). If Stop on first match is disabled and multiple schedule rules match, independent copies of the message are sent to each matching port.