Documentschanges-made-in-playlist-are-not-reflected-after-deploy
Changes made in playlist are not reflected after Deploy
If the player does not show your latest changes after Deploy, go through this checklist.
Checklist
- Deploy the right group. Playlist and asset changes reach a player only after you deploy the group that the player belongs to. You can find the player's group under Screens. See Groups.
- Player is online. An offline player receives changes the next time it connects to the server. Confirm it shows Online under Screens.
- Download is complete. The player switches to new content only after all files finish downloading. Large videos take time, and a player with a full SD card can't download.
- Schedule and validity. A playlist plays only during its scheduled time, and assets outside their validity dates are skipped. Check the group's Schedule tab. See How to schedule playlists or content.
- Download limit. When the monthly download limit is exceeded, only one deploy per day is allowed until the next billing date. See Storage space and monthly download limit per player at pisignage.com.
- Subscription credits. If your credits have run out, deploy is blocked. See Player subscription and credits and Subscriptions and Licenses.
Still not updating?
Open the player under Screens (eye icon), go to the Terminal tab and click Show Logs. Send the logs to support@pisignage.com. See Screens.