Running a product
Rollback
A deployment rollback sends traffic back to an earlier application version. It can help recover from a faulty release, but it does not automatically reverse database changes, payments or other external actions. The earlier version must still work with the current data and services.
You might see: deployment rollback, revert a release
In a real project
A new reading-list release breaks navigation, so you restore the previous deployment. Any books users added meanwhile remain in the database. You check that the earlier code can still read the current data correctly.
A common mistake
Planning to undo every problem by switching deployments. A removed database field or completed external action may need a separate recovery plan, and older code may no longer be compatible.
Put it into practice
These lessons open through your account. Your kit determines which are available.
Go to the source
Sources checked .