[Bug]: future-dated banner displays before its scheduled start (Bilietai)

[mitselek]

Summary

A banner set to start Monday 2026-06-15 started showing right away (reported 2026-06-12). Future-validFrom content displayed before its scheduled start.

Client / account / player version

• Client/account: Bilietai — Lithuania (content under the piletilevi Entu account)
• Player version: ⚠️ unknown — not captured

Reporter & date observed

Tomas Petryla (Bilietai), 2026-06-12 — email "Earlier publication".

Expected vs. actual

• Expected: blt_vjt_naujas sezonas 09 01 stays hidden until 2026-06-15 10:00.
• Actual: displayed on/around 2026-06-12, before its start.

Published CDN JSON URL

Candidate screen (only screen in the traced chain): BLT_Jaunimo_teatras
https://files.screenwerk.ee/screen/64f7f3f04ecca5c17a5980d6.json

Relevant values FROM the published JSON

Read 2026-06-18 from the live CDN JSON above (publishedAt 2026-06-12T12:56:09.015Z, max-age=60):

• playlistMedias contains only 2 entries: blt_vjt_laukine antis 06 27 and blt_vjt_delfi 08 31.
• The banner blt_vjt_naujas sezonas 09 01 is NOT present in the published JSON the player received.

Source-of-truth state (Entu CMS)

Screenshot Screenshot 2026-06-12 154831.png, captured 2026-06-12 15:48 LT (entity type = sw_playlist_media):

Field	Value
Entity	blt_vjt_naujas sezonas 09 01
Ordinal	1
Duration	8 sec
Valid From	06/15/2026, 10:00 AM
Valid To	09/01/2026, 03:27 PM

Trace identifiers

Resolved from raw api.entu.app (piletilevi account), 2026-06-18; links go to the Entu CMS:

• playlist-media: ⚠️ unresolvable — the banner's sw_playlist_media is absent from current API state. It existed at the 06-12 15:48 CMS capture but a full re-scan of all 158 playlist-media on 06-18 finds zero referencing the banner. (Entity gone; its playlist-media-level valid_from survives only in the CMS screenshot above: 06/15 10:00.)
• media: blt_vjt_naujas sezonas 09 01 — valid_from 2026-06-15T07:00:48Z (= 10:00 EEST, matches CMS); valid_to 2026-09-01T12:26:11Z; _created 2026-06-12T12:25:16Z by Tomas Petryla
• playlist: LT Jaunimo teatras playlist (currently 2 children)
• layout-playlist: 64f7f35d4ecca5c17a5980d5
• layout: 64f7f2204ecca5c17a5980d1
• schedule: 64f7f25a4ecca5c17a5980d2 (crontab 0 * * * *)
• configuration: 64f7f1174ecca5c17a5980cf
• screen-group: LT Jaunimo teatras (published.datetime 2026-06-12T12:56:09.015Z; ispublished=false)
• screen: BLT_Jaunimo_teatras (only screen in this group)

Discovery findings (2026-06-18)

Read-only investigation; facts and inference kept separate.

Facts:

1. The banner sw_media stores the correct future start — valid_from = 2026-06-15 10:00 EEST.
2. As of 2026-06-18 the banner is orphaned — no sw_playlist_media in the account references it (all 158 re-scanned).
3. The only readable published CDN snapshot (published 06-12 12:56) does not contain the banner — only the two other medias.
4. The CMS screenshot proving the banner playlist-media existed was captured 06-12 15:48, i.e. ~3 hours after that last publish.

Inference (not verified): because the playlist-media appears only after the last publish, it was likely never included in any published config. Unconfirmed — the playlist-media is deleted, there is no API audit log, and historical CDN versions cannot be read.

Net: no pipeline- or player-side defect is demonstrated — the early-displaying content is not present in any config we can see. Root cause is gated on Tomas's exact observation.

Open unknowns (root-cause phase):

• Who/what removed the banner playlist-media after 06-12 15:48? (no API audit trail)
• Tomas's exact display time + device — live player vs. CMS preview vs. cached player state?
• Did any CDN publish between 15:48 (while the playlist-media existed) and now ever carry the banner? (historical CDN not readable)

(SW:Lumiere)

[mitselek]

Investigation conclusion (2026-06-18)

Discovery and endpoint checks complete (read-only). Facts and inference kept separate.

Facts

1. Stored start is correct. The banner sw_media (6a2bfaad…) has valid_from = 2026-06-15T07:00:48Z (10:00 EEST). The future start date is stored right.
2. The banner is orphaned. As of 2026-06-18, no sw_playlist_media in the piletilevi account references it (all 158 re-scanned). The CMS screenshot proves a playlist-media existed at 06-12 15:48; it has since been removed.
3. The banner is absent from the published config on every endpoint a player could fetch. Both the 2025 web player host (files.screenwerk.ee, .ee) and the Screenwerk-2016 box host (swpublisher.entu.eu, .eu) were checked. They are byte-identical (same md5/etag c4a263…, same publishedAt 2026-06-12T12:56:09.015Z). Published playlistMedias = only blt_vjt_laukine antis 06 27 (ord 410) and blt_vjt_delfi 08 31 (ord 412). No banner.
4. Player version context. The box-office screens run the installed Screenwerk-2016 Electron player (git-pull self-update on launch; caches media to local FS, so deleted/expired content can persist on the device). Confirmed via the client install guide and the legacy code's config endpoint. The 2026 Nuxt player is not in client use.

Inference (not proven)

• The published config ordinals jump 410 → 412 (gap at 411), consistent with a third playlist-media having occupied 411 and later been removed (plausibly the banner's). Weak — these ordinals are not guaranteed contiguous.
• Because the playlist-media appears to have been created after the last publish (06-12 12:56) and removed before 06-18, it was likely never in a published config. Unconfirmed — the entity is deleted, no audit log, no historical config versions are accessible on either host.

Net

No pipeline- or player-side defect is demonstrated. The early-displaying content is not present in any config we can read. The most likely place an early display could originate is device-side — the Screenwerk-2016 box's locally-cached config (survives deletion) and/or device clock — not the published data.

Remaining unknowns (external to the codebase)

1. Whether a publish between 06-12 15:48 (while the playlist-media existed) and now briefly carried the banner — no historical config versions are accessible.
2. The on-box state of the Jaunimo teatras unit: device clock + cached local/ config. (Settle via Anydesk.)
3. Tomas's exact observation — which screen, what time, and live player vs. CMS preview. (Tomas OOO until 2026-06-23; question already sent.)

Recommendation: park until Tomas responds (2026-06-23) and/or an Anydesk look at the box, since current Entu + published-config state does not reproduce the early display.

(SW:Lumiere)