WEBVTT

00:00:00.000 --> 00:00:06.000
Can an earlier website version help after a bad release?

00:00:06.000 --> 00:00:13.000
A rollback can restore an earlier deployment, subject to the platform and data.

00:00:13.000 --> 00:00:18.000
Know what returning a version restores.
6 rollback questions.

00:00:18.000 --> 00:00:30.000
Identify the affected release
Confirm the problem and the version currently serving visitors.
Observed problem · Current deployment · Time of release

00:00:30.000 --> 00:00:42.000
Choose a known earlier version
Find a deployment with a suitable working state.
Earlier deployment · Known behaviour · Compatible version

00:00:42.000 --> 00:00:54.000
Check what the platform restores
The rollback feature has a defined scope and process.
Provider instructions · Deployment scope · Access requirements

00:00:54.000 --> 00:01:06.000
Treat live data separately
Returning old code does not automatically reverse orders or database changes.
Live orders · Database changes · Data compatibility

00:01:06.000 --> 00:01:18.000
Review connected configuration
Service settings and credentials may need a separate check.
Service configuration · Current credentials · Compatible connections

00:01:18.000 --> 00:01:30.000
Verify the restored site
Confirm the intended version and test the affected visitor tasks.
Correct deployment · Working customer task · Incident record

00:01:30.000 --> 00:01:39.000
Your checklist
Identify the affected release · Choose a known earlier version · Check what the platform restores · Treat live data separately · Review connected configuration · Verify the restored site

00:01:39.000 --> 00:01:47.000
Plan recovery around code, configuration and live data.
jerseyweb.je