What happens if an update fails?
In short and in plain language
We are ready for a failed update. Before an update, we make a backup copy. We test it first on a test copy of your shop.
If problems still come up, we go back to the last good state.
After the update, we watch your shop. This helps us spot problems early, often before customers notice.
We are prepared for an update failure rather than improvising. Before every update, we create a complete, tested backup and verify the update on staging beforehand. Should an update cause problems on the live system despite these tests, we perform a rollback to the last stable state within minutes.
In parallel, post-update monitoring detects deviations early, often before end customers notice anything, by watching critical metrics such as response times and error rates right after deployment. This combination of tested backup, fast rollback and close observation is the reason why controlled security updates are considerably less risky than untested updates applied alone.