Skip to main content
Apply for a Cheap Website
Website explainer · 1:47

Website Rollbacks Explained: Returning to an Earlier Deployed Version

Can an earlier website version help after a bad release? A rollback can restore an earlier deployment, subject to the platform and data.

Jersey Web video: An update caused a problem?

1:47 · No narration: the video shows each step as text on screen, and every step is written out below, with buttons that jump the video to it.

Download the on-screen text track (VTT)

The six points in the video

This is a silent video. The headings, explanations and labels below reproduce the information on screen.

  1. Step 1: Identify the affected release

    Confirm the problem and the version currently serving visitors.

    On-screen labels: Observed problem; Current deployment; Time of release.

  2. Step 2: Choose a known earlier version

    Find a deployment with a suitable working state.

    On-screen labels: Earlier deployment; Known behaviour; Compatible version.

  3. Step 3: Check what the platform restores

    The rollback feature has a defined scope and process.

    On-screen labels: Provider instructions; Deployment scope; Access requirements.

  4. Step 4: Treat live data separately

    Returning old code does not automatically reverse orders or database changes.

    On-screen labels: Live orders; Database changes; Data compatibility.

  5. Step 5: Review connected configuration

    Service settings and credentials may need a separate check.

    On-screen labels: Service configuration; Current credentials; Compatible connections.

  6. Step 6: Verify the restored site

    Confirm the intended version and test the affected visitor tasks.

    On-screen labels: Correct deployment; Working customer task; Incident record.

A practical check for your business

Agree which previous release can be restored and what else changed alongside it. Check content, data and connected services before assuming that restoring code alone recovers the complete business task.

Sources and further detail

Common questions

Can an earlier website version help after a bad release?

A rollback can restore an earlier deployment, subject to the platform and data. Plan recovery around code, configuration and live data.

Go further

Guide Read the practical guide More context for planning and maintaining your business website. 5 min read → Jargon Buster Rollback explained Read the related Jargon Buster explanation. Read the explanation →

Plan recovery around code, configuration and live data.

Tell Jersey Web what your website needs to do and which part you want help with.

Talk to Jersey Web →

More video tips

All 205 videos →
Length 1:47 Website development

Environment Variables Explained: Settings Outside Your Website Code

Environment variables, explained.
Length 1:47 Website development

API Keys Explained: Scope, Restrictions and Safer Website Integration

A service credential, explained.
Length 1:47 Website development

Software Dependencies Explained: The Other Code Your Website Uses

Dependencies, explained.