Critical Errors

Critical errors indicate a problem with the Commerce on cloud infrastructure project configuration that causes deployment failure, for example incorrect, unsupported, or missing configuration for required settings. Before you can deploy, you must update the configuration to resolve these errors.

Build stage

Error codeBuild stepError description (Title)Suggested action
2Can not write to the ./app/etc/env.php fileDeployment script can not make required changes to the /app/etc/env.php file. Check your filesystem permissions.
3Configuration is not defined in the schema.yaml fileConfiguration is not defined in the ./vendor/magento/ece-tools/config/schema.yaml file. Check that the config variable name is correct and defined.
4Failed to parse the .magento.env.yaml fileThe ./.magento.env.yaml file format is invalid. Use a YAML parser to check the syntax and fix any errors.
5Unable to read the .magento.env.yaml fileUnable to read the ./.magento.env.yaml file. Check file permissions.
6Unable to read the .schema.yaml fileUnable to read the ./vendor/magento/ece-tools/config/magento.env.yaml file. Check file permissions and redeploy (magento-cloud environment:redeploy).
7refresh-modulesCan not write to the ./app/etc/config.php fileThe deployment script can not make required changes to the /app/etc/config.php file. Check your filesystem permissions.
8validate-configCan not read the composer.json fileUnable to read the ./composer.json file. Check file permissions.
9validate-configThe composer.json file is missing required autoload sectionRequired autoload section is missing from the composer.json file. Compare the autoload section to the composer.json file in the Cloud template, and add the missing configuration.
10validate-configThe .magento.env.yaml file contains an option that is not declared in the schema, or an option configured with an invalid value or stageThe ./.magento.env.yaml file contains invalid configuration. Check the error log for detailed info.
11refresh-modulesCommand failed: /bin/magento module:enable --allTry to run composer update locally. Then, commit and push the updated composer.lock file. Also, check the cloud.log for more information. For more detailed command output, add the VERBOSE_COMMANDS: '-vvv' option to the .magento.env.yaml file.
12apply-patchesFailed to apply patch
13set-report-dir-nesting-levelCan not write to the file /pub/errors/local.xml
14copy-sample-dataFailed to copy sample data files
15compile-diCommand failed: /bin/magento setup:di:compileCheck the cloud.log for more information. Add VERBOSE_COMMANDS: '-vvv' into .magento.env.yaml for more detailed command output.
16dump-autoloadCommand failed: composer dump-autoloadThe composer dump-autoload command failed. Check the cloud.log for more information.
17run-balerThe command to run Baler for Javascript bundling failedCheck the SCD_USE_BALER environment variable to verify that the Baler module is configured and enabled for JS bundling. If you do not need the Baler module, set SCD_USE_BALER: false.
18compress-static-contentRequired utility was not found (timeout, bash)
19deploy-static-contentCommand /bin/magento setup:static-content:deploy failedCheck the cloud.log for more information. For more detailed command output, add the VERBOSE_COMMANDS: '-vvv' option to the .magento.env.yaml file.
20compress-static-contentStatic content compression failedCheck the cloud.log for more information.
21backup-data: static-contentFailed to copy static content into the init directoryCheck the cloud.log for more information.
22backup-data: writable-dirsFailed to copy some writable directories into the init directoryFailed to copy writable directories into the ./init folder. Check your filesystem permissions.
23Unable to create a logger object
24backup-data: static-contentFailed to clean the ./init/pub/static/ directoryFailed to clean ./init/pub/static folder. Check your filesystem permissions.
25Can not find the Composer packageIf you installed the Adobe Commerce application version directly from the GitHub repository, verify that the DEPLOYED_MAGENTO_VERSION_FROM_GIT environment variable is configured.
26validate-configRemove Magento Braintree module configuration which is no longer supported in Adobe Commerce and Magento Open Source 2.4 and later versions.Support for the Braintree module is no longer included with Magento 2.4.0 and later. Remove the CONFIG__STORES__DEFAULT__PAYMENT__BRAINTREE__CHANNEL variable from the variables section of the .magento.app.yaml file. For Braintree payment support, use an official extension from the Commerce Marketplace instead.

Deploy stage

Error codeDeploy stepError description (Title)Suggested action
101pre-deploy: cacheIncorrect cache configuration (missing port or host)Cache configuration is missing required parameters server or port. Check the cloud.log for more information.
102Can not write to the ./app/etc/env.php fileDeployment script can not make required changes to the /app/etc/env.php file. Check your filesystem permissions.
103Configuration is not defined in the schema.yaml fileConfiguration is not defined in the ./vendor/magento/ece-tools/config/schema.yaml file. Check that the config variable name is correct, and that it is defined.
104Failed to parse the .magento.env.yaml fileConfiguration is not defined in the ./vendor/magento/ece-tools/config/schema.yaml file. Check that the config variable name is correct, and that it is defined.
105Unable to read the .magento.env.yaml fileUnable to read the ./.magento.env.yaml file. Check file permissions.
106Unable to read the .schema.yaml file
107pre-deploy: clean-redis-cacheFailed to clean the Redis cacheFailed to clean the Redis cache. Check that the Redis cache configuration is correct and that the Redis service is available. See Setup Redis service.
108pre-deploy: set-production-modeCommand /bin/magento maintenance:enable failedCheck the cloud.log for more information. For more detailed command output, add the VERBOSE_COMMANDS: '-vvv' option to the .magento.env.yaml file.
109validate-configIncorrect database configurationCheck that the DATABASE_CONFIGURATION environment variable is configured correctly.
110validate-configIncorrect session configurationCheck that the SESSION_CONFIGURATION environment variable is configured correctly. The configuration must contain at least the save parameter.
111validate-configIncorrect search configurationCheck that the SEARCH_CONFIGURATION environment variable is configured correctly. The configuration must contain at least the engine parameter.
112validate-configIncorrect resource configurationCheck that the RESOURCE_CONFIGURATION environment variable is configured correctly. The configuration must contain at least connection parameter.
113validate-config:elasticsuite-integrityElasticSuite is installed, but the ElasticSearch service is not availableCheck that the SEARCH_CONFIGURATION environment variable is configured correctly, and verify that the Elasticsearch service is available.
114validate-config:elasticsuite-integrityElasticSuite is installed, but another search engine is usedElasticSuite is installed, but another search engine is configured. Update the SEARCH_CONFIGURATION environment variable to enable Elasticsearch, and verify the Elasticsearch service configuration in the services.yaml file.
115Database query execution failed
116install-update: setupCommand /bin/magento setup:install failedCheck the cloud.log and install_upgrade.log for more information. For more detailed command output, add the VERBOSE_COMMANDS: '-vvv' option to the .magento.env.yaml file.
117install-update: config-importCommand app:config:import failedCheck the cloud.log for more information. For more detailed command output, add the VERBOSE_COMMANDS: '-vvv' option to the .magento.env.yaml file.
118Required utility was not found (timeout, bash)
119install-update: deploy-static-contentCommand /bin/magento setup:static-content:deploy failedCheck the cloud.log for more information. For more detailed command output, add the VERBOSE_COMMANDS: '-vvv' option to the .magento.env.yaml file.
120compress-static-contentStatic content compression failedCheck the cloud.log for more information.
121deploy-static-content:generateCan not update the deployed versionCan not update the ./pub/static/deployed_version.txt file. Check your filesystem permissions.
122clean-static-contentFailed to clean static content files
123install-update: split-dbCommand /bin/magento setup:db-schema:split failedCheck the cloud.log for more information. For more detailed command output, add the VERBOSE_COMMANDS: '-vvv' option to the .magento.env.yaml file.
124clean-view-preprocessedFailed to clean the var/view_preprocessed folderUnable to clean the ./var/view_preprocessed folder. Check your filesystem permissions.
125install-update: reset-passwordFailed to update the /var/credentials_email.txt fileFailed to update the /var/credentials_email.txt file. Check your filesystem permissions.
126install-update: updateCommand /bin/magento setup:upgrade failedCheck the cloud.log and install_upgrade.log for more information. For more detailed command output, add the VERBOSE_COMMANDS: '-vvv' option to the .magento.env.yaml file.
127clean-cacheCommand /bin/magento cache:flush failedCheck the cloud.log for more information. For more detailed command output, add the VERBOSE_COMMANDS: '-vvv' option to the .magento.env.yaml file.
128disable-maintenance-modeCommand /bin/magento maintenance:disable failedCheck the cloud.log for more information. Add VERBOSE_COMMANDS: '-vvv' into .magento.env.yaml for more detailed command output.
129install-update: reset-passwordUnable to read reset password template
130install-update: cache_typeCommand failed: php ./bin/magento cache:enableCommand php ./bin/magento cache:enable runs only when Adobe Commerce was installed but ./app/etc/env.php file was absent or empty at the beginning of the deployment. Check the cloud.log for more information. Add VERBOSE_COMMANDS: '-vvv' into .magento.env.yaml for more detailed command output.
131install-updateThe crypt/key key value does not exist in the ./app/etc/env.php file or the CRYPT_KEY cloud environment variableThis error occurs if the ./app/etc/env.php file is not present when Adobe Commerce deployment begins, or if the crypt/key value is undefined. If you migrated the database from another environment, retrieve the crypt key value from that environment. Then, add the value to the CRYPT_KEY cloud environment variable in your current environment. See Adobe Commerce encryption key. If you accidentally removed the ./app/etc/env.php file, use the following command to restore it from the backup files created from a previous deployment: ./vendor/bin/ece-tools backup:restore CLI command ."
132Can not connect to the Elasticsearch serviceCheck for valid Elasticsearch credentials and verify that the service is running
137Can not connect to the OpenSearch serviceCheck for valid OpenSearch credentials and verify that the service is running
133validate-configRemove Magento Braintree module configuration which is no longer supported in Adobe Commerce or Magento Open Source 2.4 and later versions.Support for the Braintree module is no longer included with Adobe Commerce or Magento Open Source 2.4.0 and later. Remove the CONFIG__STORES__DEFAULT__PAYMENT__BRAINTREE__CHANNEL variable from the variables section of the .magento.app.yaml file. For Braintree support, use an official Braintree Payments extension from the Commerce Marketplace instead.
134validate-configAdobe Commerce and Magento Open Source 2.4.0 require Elasticsearch service to be installedInstall Elasticsearch service
138validate-configAdobe Commerce and Magento Open Source 2.4.4 requires OpenSearch or Elasticsearch service to be installedInstall OpenSearch service
135validate-configThe search engine must be set to Elasticsearch for Adobe Commerce and Magento Open Source >= 2.4.0Check the SEARCH_CONFIGURATION variable for the engine option. If it is configured, remove the option, or set the value to “elasticsearch”.
136validate-configSplit Database was removed starting from Adobe Commerce and Magento Open Source 2.5.0.If you use split database you have to revert to or migrate to a single database or use an alternative approach.
139validate-configIncorrect search engineThis Adobe Commerce or Magento Open Source version does not support OpenSearch. You must use versions 2.3.7-p3, 2.4.3-p2, or later

Post-deploy stage

Error codePost-deploy stepError description (Title)Suggested action
201is-deploy-failedDeploy stage failed
202The ./app/etc/env.php file is not writableDeployment script can not make required changes to the /app/etc/env.php file. Check your filesystem permissions.
203Configuration is not defined in the schema.yaml fileConfiguration is not defined in the ./vendor/magento/ece-tools/config/schema.yaml file. Check that the config variable name is correct, and that it is defined.
204Failed to parse the .magento.env.yaml fileThe ./.magento.env.yaml file format is invalid. Use a YAML parser to check the syntax and fix any errors.
205Unable to read the .magento.env.yaml fileCheck file permissions.
206Unable to read the .schema.yaml file
207warm-upFailed to preload some warm-up pages
208time-to-firs-byteFailed to test time to first byte (TTFB)
227clean-cacheCommand /bin/magento cache:flush failedCheck the cloud.log for more information. Add VERBOSE_COMMANDS: '-vvv' into .magento.env.yaml for more detailed command output.

General

Error codeGeneral stepError description (Title)Suggested action
243Configuration is not defined in the schema.yaml fileCheck that the config variable name is correct, and that it defined.
244Failed to parse the .magento.env.yaml fileThe ./.magento.env.yaml file format is invalid. Use a YAML parser to check the syntax and fix any errors.
245Unable to read the .magento.env.yaml fileUnable to read the ./.magento.env.yaml file. Check file permissions.
246Unable to read the .schema.yaml file
247Unable to generate a module for eventingCheck the cloud.log for more information.
248Unable to enable a module for eventingCheck the cloud.log for more information.
249Failed to generate the AdobeCommerceWebhookPlugins moduleCheck the cloud.log for more information.
250Failed to enable the AdobeCommerceWebhookPlugins moduleCheck the cloud.log for more information.

Warning Errors

Warning errors indicate a problem with the Commerce on cloud infrastructure project configuration such as incorrect, deprecated, unsupported, or missing configuration settings for optional features that can affect site operation. Although a warning does not cause deployment failure, you should review warning messages and update the configuration to resolve them.

Build stage

Error codeBuild stepError description (Title)Suggested action
1001validate-configFile app/etc/config.php does not exist
1002validate-configThe ./build_options.ini file is no longer supported
1003validate-configThe modules section is missing from the shared config file
1004validate-configThe configuration is not compatible with this version of Magento
1005validate-configSCD options ignored
1006validate-configThe configured state is not ideal
1007run-balerBaler JS bundling can not be used

Deploy stage

Error codeDeploy stepError description (Title)Suggested action
2001pre-deploy:cacheCache is configured for a Redis service that is not available. Configuration will be ignored.
2002validate-configThe configured state is not ideal
2003validate-configThe directory nesting level value for error reporting has not been configured
2004validate-configInvalid configuration in the ./pub/errors/local.xml file.
2005validate-configAdmin data is used to create an admin user during initial installation only. Any changes to Admin data are ignored during the upgrade process.After the initial installation, you can remove admin data from the configuration.
2006validate-configAdmin user was not created as admin email was not setAfter installation, you can create an admin user manually: Use ssh to connect to your environment. Then, run the bin/magento admin:user:create command.
2007validate-configUpdate php version to recommended version
2008validate-configSolr support has been deprecated in Adobe Commerce and Magento Open Source 2.1.
2009validate-configSolr is no longer supported by Adobe Commerce and Magento Open Source 2.2 or later.
2010validate-configElasticsearch service is installed at infrastructure layer, but it is not used as a search engine.Consider removing the Elasticsearch service from the infrastructure layer to optimize resource usage.
2011validate-configElasticsearch service version on infrastructure layer is not compatible with current version of the elasticsearch/elasticsearch module, used by your Adobe Commerce application.
2012validate-configThe current configuration is not compatible with this version of Adobe Commerce
2013validate-configSCD options ignored because the deploy process did not run on the build phase
2014validate-configThe configuration contains deprecated variables or values
2015validate-configEnvironment configuration is not valid
2016validate-configJSON type configuration can not be decoded
2017validate-configThe current configuration is not compatible with this version of Adobe Commerce
2018validate-configSome services have passed EOL
2019validate-configThe MySQL search configuration option is deprecatedUse Elasticsearch instead.
2029validate-configSplit Database was deprecated in the Adobe Commerce and Magento Open Source 2.4.2 and will be removed in 2.5.If you use split database you should start planning to revert to or migrate to a single database or use an alternative approach.
2020install-updateAdobe Commerce installation completed, but the app/etc/env.php configuration file was missing or empty.Required data will be restored from environment configurations and from the .magento.env.yaml file.
2021install-update:db-connectionFor split databases used custom connections
2022install-update:db-connectionYou have changed to a database configuration that is not compatible with the slave connection.
2023install-update:split-dbEnabling a split database will be skipped.
2024install-update:split-dbThe SPLIT_DB variable is missing the configuration for split connection types.
2025install-update:split-dbSlave connection not set.
2026pre-deploy:restore-writable-dirsFailed to restore some data generated during the build phase to the mounted directoriesCheck the cloud.log for more information.
2027validate-config:mage-mode-variableMode value for MAGE_MODE environment variable not supportedRemove the MAGE_MODE environment variable, or change its value to “production”. Adobe Commerce on cloud infrastructure supports “production” mode only.
2028remote-storageRemote storage could not be enabled.Verify remote storage credentials.
2030validate-configElasticsearch and OpenSearch services are both installed at infrastructure layer. Adobe Commerce and Magento Open Source 2.4.4 and later use OpenSearch by defaultConsider removing the Elasticsearch or OpenSearch service from the infrastructure layer to optimize resource usage.