Le contenu programmé ne se lance pas.

You built the event, the calendar shows it, and the screen is playing something else. There is a defined set of reasons for this, and working through them in order usually settles it.

Everything that has to be true

Content reaches a screen only when all five hold at the same moment:

1. The layout is published. Edits sit in a draft until you publish them, and drafts never leave the CMS.
2. The display is authorised and checking in. A player that registered but was never connected through Add a display is inert, it downloads nothing.
3. The event targets this display, or a display group it is genuinely a member of. Membership changes quietly when somebody reorganises, so check it rather than assume it.
4. The event covers the current time, in the timezone the event is measured against, which is not always the one you were reading.
5. Nothing of higher priority is overriding it, in the narrow sense below.

Fail any one and the layout is skipped silently, there is no on-screen error, you get the default layout or the splash screen.

Priority only beats its own event type

A higher number wins, with 0 the lowest, but it only overrides events of the same Event Type, with layouts, campaigns, images, videos and playlists all counting as one type. Overlays, interrupts and commands are separate types, so no amount of priority on your main content pushes a persistent strap aside, an overlay is meant to sit on top.

Watch out The trap here is a recurring always-on event given a high priority months ago. It quietly suppresses everything scheduled since. Open the Schedule in Agenda View for that display and read what is genuinely active.

Display order decides what plays first

When several events are concurrent and none outranks the others, Display Order sets the sequence. It is a simple numerical sort, lowest to highest, so an event marked 1 plays before one marked 2. Left blank, events fall back to the order they were first added, which is why a new event often turns up last in the loop rather than not at all. If the right content plays in the wrong order, this is the field, not priority.

CMS time or the screen’s local time

An event is measured against one of two clocks, and the choice sits on the event itself, usually labelled Run at CMS Time. Run on CMS time, the event fires at the same instant everywhere, which is what a national campaign wants. Left to sync instead, it follows each display’s own timezone, which is what opening hours and lunch menus need. Read Timezones, Dayparting and Schedule Accuracy before rebuilding the event.

Dayparts, and the exceptions inside them

A daypart is a named time band you schedule against instead of typing times repeatedly, built from Dayparting with Add Daypart. A daypart can carry Exceptions: different timings on selected days. A breakfast daypart running 07:00 to 10:00 might be set differently at the weekend. Check the daypart before blaming the event. Editing its times or exceptions updates existing future events that use it, so one small change reaches every screen.

If the content should run all the time, choose Always rather than a custom window.

Scheduled, but invalid

A layout can be correctly scheduled and still rejected by the player. Before it will play it must be valid and published, downloaded in full along with every file it depends on, and none of those files sitting on the player’s Faultlist. Open the player’s status window and read Schedule Status. It groups layouts as all, scheduled, valid and invalid. A layout listed under scheduled but not valid is being rejected, not ignored. See Reading the Player Status Window. In the CMS an orange exclamation mark on a layout is not proof of a fault, it is expected on anything carrying online content such as a webpage.

Recurrence that stopped

Open the event and check its Repeats. The Until field ends the recurrence, and an Until date now in the past means the event stopped repeating with no warning and no trace on today’s calendar. Set it after the final repetition you want, and after the end of that last playback, an Until time landing mid-event cuts the content short.

How long to wait, and the fastest test

Allow one full collection interval plus the download, longer for a heavy video. If the switchover is late rather than missing, the layout on screen is usually still scheduled and holding a long-running item, which must finish before the next event starts.

Tip To prove the whole chain end to end, schedule a single-image layout to that one screen with Always and nothing else set. If that plays, the plumbing is fine and the fault is in the event you were debugging. If that plays, the fault is in your original event. If it does not, this is not a scheduling problem, go to Display Is Online but Content Never Changes. Still stuck, send us the display name and the event through the support request form.

Related articles: Scheduling Content, Scheduling Your First Content, Timezones, Dayparting and Schedule Accuracy