Rollforward vs Rollback Strategies
When a release causes a problem, there are two ways to respond: roll back to the previous version, or roll forward by quickly releasing a fix. Both are valid, and the right choice depends on the situation.
Having both options ready means we can react in whatever way restores service fastest.
Two Ways to Recover
Rollback returns to the last known-good version and is usually the safest, fastest option. Rollforward keeps the new version and applies a small fix on top, which suits cases where reverting is impractical — for example after a one-way database change.
In practice we decide in the moment, guided by which path restores normal service to your customers soonest. Having both options prepared means we are never forced into a slow or risky recovery just because only one route was available.
| Strategy | Action | Best when |
|---|---|---|
| Rollback | Return to previous version | Reverting is clean and quick |
| Rollforward | Ship a small fix on top | A change cannot easily be undone |
Frequently Asked Questions
Which do you default to?
Rollback, because it is usually the fastest and lowest-risk way to restore service. We roll forward only when reverting is not viable.
If you need a hand with any of this, your Progressive Robot delivery team is ready to help. Raise a ticket from the Support area of your client portal or speak to your account manager and we will guide you through the next steps.