Scheduling conflicts occur when multiple content items compete for the same screen at the same time, or when content plays outside its intended time window. The root causes are usually: overlapping schedules without priority settings, incorrect timezone configuration, NTP clock drift, or misunderstood day-of-week numbering. SpinetiX handles conflicts through a priority-based system — higher-priority content always overrides lower-priority content.
How SpinetiX Scheduling Works
Priority-Based Resolution
Every scheduled item has a priority level. When two items overlap in time, the higher-priority item plays. When the higher-priority item's schedule ends, the lower-priority item resumes. Set priority levels deliberately: emergency (highest) → event-specific → campaign → default (lowest).
Default/Fallback Content
Default content plays when no scheduled item is active. This is the "always on" baseline. Without a default, screens go blank between scheduled items. Always configure a default playlist — even if it's just a branded screensaver.
Time-Based Scheduling
Schedule by: time of day (morning/afternoon/evening), day of week (weekday/weekend), date range (campaign start/end), or recurring pattern (every Monday). Combine these for precise targeting: "summer campaign, weekdays only, lunch hours (11:00–14:00)."
Common Conflict Scenarios
| Scenario | Cause | Fix |
|---|---|---|
| Wrong content showing | Schedule overlap with equal priority | Set explicit priorities |
| Content plays 4 hours late | Timezone set to UTC | Set correct timezone in player settings |
| Content plays at random times | NTP not configured, clock drifted | Enable NTP time synchronization |
| Weekend content on weekday | Day numbering mismatch (0=Sun vs 1=Mon) | Verify day numbering convention |
| Blank screen between items | No default/fallback playlist | Add default baseline playlist |
| Emergency content won't play | Priority too low | Set emergency to highest priority |
Key Parameters
| Parameter | Value | Why It Matters |
|---|---|---|
| Priority levels | Numeric (higher = wins) | Conflict resolution mechanism |
| Timezone | Player setting (e.g., Asia/Dubai) | Schedules use local time |
| NTP | Enabled, pool.ntp.org | Accurate clock for schedule timing |
| Default playlist | Always-on baseline | Prevents blank screen gaps |
| Schedule granularity | Minute-level | Precise day-parting |
Common Mistakes
- All schedules at the same priority. If everything is priority 5, the system can't resolve overlaps predictably. Use a clear priority hierarchy: emergency (10) → events (7) → campaigns (5) → default (1).
- Timezone mismatch. A player in Dubai (GMT+4) set to UTC plays 9:00 AM content at 1:00 PM local time. Always set the correct timezone in player network/system settings.
- No NTP sync. Without NTP, the player's clock drifts minutes per week. After a few months, schedules are off by significant amounts. Always enable NTP time synchronization.
- Gaps between schedule blocks. Scheduling content 9:00–12:00 and 13:00–17:00 leaves 12:00–13:00 blank (no default). Either add content for the gap or ensure a default playlist covers inactive periods.