Skip to content

Scheduler

The scheduler lets you automate MZAP operations on a time-based trigger system.

  • Once — Run at a specific date and time
  • Daily — Run every day at a set time
  • Weekly — Run on specific days of the week
  • Interval — Run every N minutes/hours
  • Cron — Full cron expression for complex schedules
  • Prayer Time — Run daily at one of the five Islamic prayer times, computed from the venue’s location (see below)

For Daily and Weekly triggers, the task’s start time is an activation date, not the exact firing instant. If you create a Daily task at 15:56:00 with trigger time 15:56, it fires today at 15:56 (in the task’s timezone) — not tomorrow. A future start date still gates the trigger: a Daily task with a start date in the future won’t fire until that date arrives.

Scheduled tasks can perform these actions:

  • PlayerControl — Play, pause, stop, or adjust player volume
  • ZoneControl — Adjust zone volume or mute state
  • LoadWorkspace — Load a saved workspace
  • JinglePlay — Play a jingle
  • RoutingControl — Attach or detach player-zone connections

Prayer Time triggers fire daily at one of the five Islamic prayer times — Fajr, Dhuhr, Asr, Maghrib, Isha — or at Sunrise, which is also offered as a reference time. Times are recomputed from astronomical formulas every day for the venue’s latitude and longitude, so there is no hardcoded schedule to maintain. This is intended for malls, hotels, and venues in MENA markets that need automatic adhan playback or music suppression at prayer time.

Before you can pick a Prayer Time trigger, set the venue location and calculation method in Settings → Prayer-Time Scheduling. See the Prayer-Time Scheduling settings for the full reference.

  1. Open Scheduler and create a new task.
  2. Set Trigger Type to Prayer Time.
  3. Pick the prayer (Fajr, Sunrise, Dhuhr, Asr, Maghrib, or Isha).
  4. Set an Offset (minutes) — negative runs the task that many minutes before the prayer, positive runs it after, 0 runs at the prayer time exactly. Useful for warning chimes (e.g. -5 for “five minutes before Maghrib”) or post-adhan resume cues.
  5. Pair with any action: JinglePlay to play the adhan, PlayerControl to pause music, ZoneVolume to drop a zone, etc.

The next run time is recomputed automatically each day from the current day’s prayer times — no manual updating required.

When the trigger type is Prayer Time, the Start time and End time fields become Active from and Active until date pickers. Leave them empty to run year-round, or set them to limit the trigger to a date range — for example, set Active from to the first day of Ramadan and Active until to the last day so the trigger only fires that month.

”Music stops, prayer plays, music returns”

Section titled “”Music stops, prayer plays, music returns””

For the common workflow where music ducks completely while the adhan plays and then returns:

  1. Create a jingle for the adhan and set its Duck Level to 0% — this fully silences the underlying music while the jingle plays, then restores it.
  2. Schedule a Prayer Time trigger with a JinglePlay action that plays the adhan jingle.

For internet streams, the stream keeps decoding silently underneath the duck so playback resumes instantly with no reconnect lag.

The task editor offers two ways to save:

  • Save writes the task in place and shows a brief “Saved” indicator, so you can keep tweaking the same task.
  • Save & close saves the task and returns you to the task list in one click.

When editing an existing task, the Cancel button is relabeled Back to tasks — pressing it returns to the list (your changes were already committed by Save).

Click the copy icon in a task row’s action column (between the trigger and delete buttons) to clone that task. The clone copies every field — trigger, action, parameters, targets, schedule, and repeat count — and is created disabled with a “(copy)” suffix on its name. Review the clone and enable it when you’re ready.

Duplicating, like creating, editing, and deleting tasks, is admin-only.

All task executions are logged with timestamps and results for auditing and troubleshooting.