Skip to content
NovaVMS Manual

Limit when an alert rule evaluates

Use this procedure when an alert should evaluate only on selected days or during selected hours — for example, a loading-dock alert that matters only after business hours.

Rule schedules control alert evaluation only. They do not start, stop, or schedule camera recording. Events can still be recorded outside the rule’s time window.

Procedure

  1. Go to Alerts → Rules.
  2. Click New Alert (NL wizard). Confirm the browser opens /alerts/rules/new-v5.
  3. Select the sites and cameras the rule watches.
  4. In the description step, include the days, start time, end time, and timezone. For example: Alert when a person is on the loading dock from 20:00 to 06:00 on weekdays in Asia/Taipei.
  5. Compile the rule and review its time_windows values. Confirm the weekdays, start, end, and IANA tz match what you intended.
  6. Test the compiled rule against recent events. Events outside the window should appear as time-window mismatches rather than notifications.
  7. Have an Admin or Owner finish the remaining steps and click Save & Activate in the same session. The active compiled version is what the evaluator reads.

An Operator can compile and test the rule, but cannot complete activation. Save as draft persists an inactive compiled version that the current Rules page does not list and the wizard cannot reopen, so it is not a usable handoff to an Admin or Owner. Start this procedure while signed in as an Admin or Owner when the rule must go live.

Common variations

  • Overnight windows: state the full overnight intent in the description and confirm the compiled time_windows output before activation.
  • Different schedules per camera: create one compiled rule per schedule and scope each rule to the relevant cameras.
  • Cameras in multiple timezones: a compiled rule uses one timezone for its recurring window. Confirm the timezone warning and create separate rules when cameras need different local windows.

If this didn’t work

  • If the compiled preview has the wrong days, hours, or timezone, go back to the description and state them explicitly, then compile again.
  • If a time-restricted legacy rule never fires, recreate it through /alerts/rules/new-v5; do not use the legacy Business hours option.
  • If the compiled rule does not fire during the expected window, confirm it is active and use the test step to inspect the evaluator reason.