Delay Timers
Delay Timers are optional control mechanisms used to define how and when specific actions are executed after an event is triggered. Unlike conditions and schedules, delay timers are not pre-configured globally; instead, they are defined per rule using the Event & Action Configurator.
Setting the Timer
To apply a timer to one or more actions:
Open the Rules section.
Select the desired rule(s).
In the Event & Action Configurator, select one or more events (use Ctrl+click or Shift+click to select multiple).
Click the Timer button in the bottom panel to open the Set Timer dialog box.
Action delay time
Specify how long the system should wait before executing the action after an event is triggered.
Set the delay using the keyboard or scroll over the time fields (hours, minutes, seconds).
This delay applies individually per action.
Maximum delay interval is 24 hours.
Server restart will reset the Action delay timer!!!
Delay Mode
Choose how the system responds to multiple identical events while a delay is active:
Run after each event: Every new event schedules its own delayed action, even if one is already in progress.
Restart delay on new event: If an action is already delayed, the timer is reset. Only one action will be executed once the delay expires without new matching events.
Action cooldown interval
Defines the minimum interval between consecutive executions of the same action.
If a new event is triggered within this period, it is ignored.
This is useful to prevent excessive action execution during high-frequency event bursts.
Behavior Scenarios
Below are common configuration examples that illustrate how timer settings affect action behavior.
Postpone
Action delay time: Set
Delay mode: Run after each event
Action cooldown interval: Not set
Each event triggers its own action after the specified delay.
Best used when every event deserves a delayed response.
Example: Each motion detection sends an alert after 10 seconds, even if many occur.
Extend
Action delay time: Set
Delay mode: Restart delay on new event
Action cooldown interval: Not set
The delay is restarted with each new event. The action is only executed once no new events arrive during the whole delay period.
Ideal for merging bursts of repeated events into a single action.
Example: Repeated recording errors postpone log writing until errors stop.
Cooldown only
Action delay time: Not set
Delay mode: Run after each event
Action cooldown interval: Set
The first matching event triggers the action immediately.
Subsequent events within the cooldown interval are ignored.
Use this to limit the frequency of repeated actions.
Example: One alarm is triggered per minute, even if multiple events occur.
Postpone + Extend
Action delay time: Set
Delay mode: Restart delay on new event
Action cooldown interval: Optional
The timer is restarted on every new event, and the action will execute only after no matching events occur during the full delay.
Cooldown can add an extra pause before the rule can trigger again.
Best for suppressing noisy event periods and reacting only once things calm down.
Example: Send a single alert 30 seconds after people stop entering a restricted area.
Postpone + Cooldown
Action delay time: Set
Delay mode: Run after each event
Action cooldown interval: Set
Each event triggers a delayed action, but once the action is executed, further actions are blocked for the cooldown interval.
Useful when a delayed response is needed, but you want to prevent repeated execution.
Example: Lock the door 10 seconds after access is denied, but don’t retry for 1 minute.
Last updated