TV or screen still shows the old version

What you may be seeing

• The editor or Data tab shows the new content but a paired screen still shows an older version.
• Screens shows the device one or more feed versions behind, or deployment says updating/error/no report.

What usually causes it

• The change was saved but the board was not published. Save protects editor work; Publish creates the release players receive.
• The screen is offline, so its cached content keeps playing but new releases cannot arrive.
• The screen is still downloading the new release, especially when a release contains large video.
• The screen is pinned to an older release for testing instead of following the board's latest release.
• The screen is assigned to a different board than the one that was edited.
• The screen is over the plan limit and has been placed into the screen-limit state.
• The player reported an error while downloading, validating, or activating the release.

Do this

1. Open Screens and find the affected screen. Confirm it is online and assigned to the board you changed.
2. Compare the screen's feed version with the target/latest version and read its deployment chip: active, updating, error, or no report.
3. If the board was only saved, open the board and press Publish. Publishing creates the release that screens can receive.
4. If the device is pinned, open its release pin control and choose the option to follow the board's latest release again.
5. If deployment says updating, leave the pairing alone and let the current download finish before doing anything destructive.
6. If the screen is online but remains behind or reports an error, use the screen card's Reload command. Use Clear cache only after Reload does not recover it or diagnostics point to cache corruption.
7. If the screen is offline, fix power/network first. Do not re-pair a normally paired offline screen just to force an update.

You know it is fixed when

• Screens shows deployment active and the device feed version matches its target/latest version.
• The physical display shows the newly published content.

When this is probably a real support issue

• The screen is online, unpinned, assigned to the correct board, has a valid target release, and repeatedly remains in deployment error after Reload.
• Multiple unrelated online screens fail to receive the same new release.