FAQ and caveats

#Does uploading a presentation put it on the players?

No. Uploading adds approved published content to the presentation library. Nothing changes on a player until you select targets, select the presentation, run a dry run and deploy.

#Does a successful deployment mean the screen has changed?

Not necessarily. A successful BrightBridge job means the release was prepared for the selected player. The player still needs to contact the platform, collect the content and begin playback.

#How should temporary event players and content be named?

Dates can help when the same event name is reused, but location and purpose are usually more useful while operating the show.

#Why are more players selected than I can see?

Filtering changes which rows are visible. It may not remove players already selected before the filter changed.

1. 1
   Stop before running the action.
2. 2
   Read the selected count.
3. 3
   Clear the selection if the scope is uncertain.
4. 4
   Clear and reapply the intended filters.
5. 5
   Select the targets again and compare the count with the approved list.

#When do I need to run the dry run again?

Run it again after changing any target player, presentation, variable override, rewrite setting or advanced deployment option. The preview describes the inputs that existed when it ran; it cannot approve later edits.

#Does offline always mean something is broken?

No. Temporary event equipment may be packed down, a permanent screen may be outside its operating schedule, or a player may simply not have reported recently enough.

• Compare the state with the event schedule, venue access and expected power state.
• Look at the most recent activity time rather than the badge alone.
• Compare other players on the same network or site.
• Treat an unexpected change from the known state as the useful signal.

#Should I click again when something is taking a while?

Usually not. Uploads, dry runs, deployments, rollback, snapshots and Liveview can take time. Repeated clicks can start duplicate work or make the result harder to understand.

#What if I refresh or close the browser during an action?

Do not assume the action stopped. BrightBridge may have already started server-side work.

1. 1
   Return to the same workspace.
2. 2
   Check whether a job or result already exists.
3. 3
   Review recent events or logs around the start time.
4. 4
   Check player activity before starting the action again.
5. 5
   Retry only when you have confirmed no current or completed job covers the same scope.

#Will reboot fix an offline player or failed Liveview?

Maybe, but reboot is not a general first step. An offline player may not receive the command, and a failed Liveview can have a viewing-path problem while the player continues playing normally.

• Try status, activity, ping or snapshot first.
• Confirm the correct player and the acceptable interruption window.
• Issue one reboot only.
• Wait for fresh activity and verify playback afterward.

#What does rollback restore—and what might it not restore?

Rollback restores retained player content from a known restore point. Separately managed player values may have their own lifecycle and may not automatically match the restored content version.

#When is it safe to delete a player, presentation, tag or preset?

Only when its operational and recovery value is understood. Temporary does not automatically mean disposable.

#What should I include when asking for help?