Cause

The issue is caused by the backward incompatible changes in the Fastly module v1.2.79.

Solution

Upgrade the Fastly module to version 1.2.82 or higher.

To do this, take the following steps:

  1. Execute one of the following commands:

    • if the Fastly module is included to the magento-cloud-metapackage:
      composer update magento/magento-cloud-metapackage
      
    • if the Fastly module was installed separately (for example, in case you are using Adobe Commerce on-premises, not the cloud edition)
      composer update fastly/magento2
      
  2. Commit and push the changes, and trigger the deployment process if it is not done automatically.

  3. In the Admin, upload the new VCL to Fastly.

Previous pageThe 'Current version of RDBMS not supported' error on deployment
Next pageEnvironment redeployment failed or MySQL server gone away

Commerce


Connect with Experience League at Summit!

Get front-row access to top sessions, hands-on activities, and networking—wherever you are!

Learn more