Priorities & Conflicts
When two or more schedule entries are active on the same screen at the same moment, Veyli picks exactly one winner using these rules, in order:
| # | Rule | Example |
|---|---|---|
| 1 | Emergency override always wins | Fire evacuation notice |
| 2 | Higher priority (1–10, 10 wins) | Black Friday takeover (8) beats the regular menu (5) |
| 3 | More specific target — an entry for the screen beats one for its group | A promo on Checkout 2 beats the store-wide loop |
| 4 | Most recently published | The schedule you published last wins a tie |
If no entry is active, the screen plays its default content.
Worked example
Screen Downtown – Menu 1 (group Downtown store), Wednesday 12:30:
| Entry | Target | Time | Priority | Active? |
|---|---|---|---|---|
| Lunch menu | Group | 11:00–16:00 | 5 | Yes |
| Weekday lunch promo | Screen | Mon–Fri 12:00–14:00 | 5 | Yes |
| Breakfast menu | Group | 06:00–11:00 | 5 | No |
Both active entries have priority 5, so rule 3 applies: the screen-level Weekday lunch promo wins. At 14:00 it ends and Lunch menu takes over.
Good practice
- Leave the default priority (5) alone for everyday content. Reserve 8–10 for campaigns that must win.
- Prefer group-level schedules; use screen-level entries only for genuine exceptions.
- Check the Timeline of a screen before launches.
Want to build intuition? The Conflict playground lets you toggle entries, change priorities and scrub through the day to see who wins.