Topic 1 of 5

#When rollback is appropriate

  • The new presentation is visibly incorrect and a known-good restore point exists.
  • The impact of waiting for a corrected release is greater than restoring the previous content.
  • The affected player is identified and the recovery action is approved.
  • The operator understands that other player settings may need separate review.
Topic 2 of 5

#Choose the restore point

Topic 3 of 5

#Run the rollback

  1. 1
    Open the rollback area and select one affected player.
  2. 2
    Load its available restore points.
  3. 3
    Select the verified known-good item.
  4. 4
    Read the confirmation and start the restore once.
  5. 5
    Wait for the final result before performing another recovery action.
Topic 4 of 5

#Verify the recovery

  1. 1
    Watch for fresh player activity.
  2. 2
    Confirm the restored presentation identity.
  3. 3
    Visually verify the physical display, snapshot or Liveview.
  4. 4
    Review any managed player values that could remain separate.
  5. 5
    Record the cause, restore point and verification result.
Topic 5 of 5

#Know the limits