Practical guide
Plan a restart after a software update
A post-update restart should verify the workflow that changed and retain a practical recovery path if the new setup fails.
A post-update restart should verify the workflow that changed and retain a practical recovery path if the new setup fails.
A practical procedure
-
Save the previous working configuration and note the update version before applying it.
-
Restart privately and test media loading, sound routing, one answer and the intended output.
-
Record changed behaviour and postpone public use when an essential step cannot be reproduced.
Worked example: a fictional session
A fictional team updates after the final session of the day, then rehearses the next session before accepting the new configuration.
Check the limits
A successful application launch does not verify the full production workflow.