This is a beta release of documentation for Magento 2.4, published for previewing soon-to-be-released functionality. Content in this version is subject to change. Links to the v2.4 code base may not properly resolve until the code is officially released.

You must install and configure Elasticsearch 7.6.x before upgrading to Magento Commerce or Magento Open Source 2.4.0. See Check the catalog search engine for details.

Roll back after update failure

Edit on GitHub

Log an Issue

If your component update fails, messages similar to the following display in the Console Log:

[2015-08-14 12:12:02 CDT] Job "update {"components":[{"name":"example/module","version":"1.1.0"}]}" has been started
[2015-08-14 12:12:02 CDT] Starting composer update...
[2015-08-14 12:12:02 CDT] An error occurred while executing job "update {"components":
[{"name":"example/module","version":"1.1.0"}]}": Could not complete update {"components":
[{"name":"example/module","version":"1.1.0"}]} successfully: Cannot find component to update

In the preceding example, there is no component version to which to roll back. Contact the component vendor or try to resolve the issue yourself.

Meantime, you can roll back to a previous backing by clicking Rollback. Magento recovers your data even if you did not back up previously.