Upgrade To 2.4.7-p3 | Deployment | Algolia | The key is not present in the schema

[kashif_mkk]

We have upgraded to 2.4.7-p3 | Magento Cloud.

Algolia extension is installed.

While deployment, getting the following warning message.

Validating configuration files
W: algolia: The key is not present in the schema

The site and Algolia search are working fine.

Please check.

[johnwebdes40a5]

Hello @kashif_mkk 

The warning you're seeing during deployment, "W: algolia: The key is not present in the schema", typically occurs when there's a configuration issue related to the Algolia extension in your Magento Cloud environment. The key could either be missing from the Algolia configuration, or there might be a mismatch in the configuration files.

Magento Admin panel

Go to your Magento Admin panel and navigate to Stores > Configuration > Algolia Search.  Ensure that all the required fields, such as API Key, Application ID, and Index Prefix, are filled correctly.

Review env.php File

On your Magento instance, check the app/etc/env.php file.

Ensure the Algolia configuration is correctly defined in this file. For example:

'algolia' => [

    'application_id' => 'YourAppID',

    'search_only_api_key' => 'YourSearchKey',

    'index_prefix' => 'your_index_prefix',

]

Check for Module Compatibility with Magento 2.4.7-p3

Ensure that the version of the Algolia extension installed is fully compatible with Magento 2.4.7-p3.

composer update algolia/algoliasearch-magento-2

Hope it helps ! 

If you find our reply helpful, please give us kudos.

A Leading Magento Development Agency That Delivers Powerful Results, Innovation, and Secure Digital Transformation.

WebDesk Solution Support Team

Get a Free Quote | | Adobe Commerce Partner | Hire Us | Call Us 877.536.3789

[kashifmagef191]

Dear @johnwebdes40a5 

Thanks for your comments.

FYI, the Algolia is working fine.

Under -> Admin -> Algolia, all the information is saved.

Yes, the env.php does not exist the Algolia Keys.

This warning only appears at the time of running deployment and at the very beginning.

This is strange.

Validating submodules

Validating configuration files
W: algolia: The key is not present in the schema

Processing activity: Jimmy pushed to Staging
Found 1 new commit

W: algolia: The key is not present in the schema
Building application 'mymagento' (runtime type: php:8.2, tree: b37d228)
Generating runtime configuration.

Please check.

Thanks,

[johnwebdes40a5]

Hello @kashifmagef191 

In Magento 2, if you encounter a warning during deployment that the env.php does not contain the Algolia keys.

If the keys are configured in the Magento Admin Panel, but the warning still appears, it might indicate that the configuration is not being written to the env.php file during deployment.

You can manually add the Algolia keys in the app/etc/env.php file. 

'algolia' => [

    'enabled' => true,

    'application_id' => 'your_algolia_application_id',

    'api_key' => 'your_algolia_api_key',

    'search_api_key' => 'your_algolia_search_api_key',

    'index_prefix' => 'your_index_prefix', // Optional

],

​Hope it helps ! 

If you find our reply helpful, please give us kudos.

A Leading Magento Development Agency That Delivers Powerful Results, Innovation, and Secure Digital Transformation.

WebDesk Solution Support Team

Get a Free Quote | | Adobe Commerce Partner | Hire Us | Call Us 877.536.3789

[Milople]

Hello @kashif_mkk,

The warning W: algolia: The key is not present in the schema during deployment on Magento 2.4.7-p3 with the Algolia extension installed suggests that the Algolia configuration is not properly defined in the expected schema, likely within the Magento Cloud configuration files.

Since the Algolia search functionality and admin settings are working fine, this warning is likely benign but should be addressed to ensure a clean deployment process.

Magento Cloud uses a validation mechanism to check if config keys are valid according to a predefined schema (schema.yaml). If a key (like algolia) is not part of that schema — even if it’s valid in your Magento app — it triggers this warning.

Even though the extension works fine, the schema validation doesn’t recognize it because:

• It’s a third-party extension (Algolia).
• No schema definition for algolia exists in vendor/magento/magento-cloud-components/etc/schema.yaml.

If you want to eliminate the warning (optional, not necessary), you can:

1. Add a placeholder schema entry manually (not recommended unless you're customizing Magento Cloud scripts).
2. Reach out to Algolia support to see if they provide a schema.yaml snippet for Cloud compatibility.

The env.php file (app/etc/env.php) is used to store environment-specific configurations in Magento. If the Algolia keys are missing here, adding them might resolve the schema validation warning.

Add the Algolia configuration under the algolia key. The structure depends on your Algolia setup but typically includes the application ID, API key, and search key.

Example:

'algolia' => [ 'enabled_frontend' => 1,
                     'enabled_backend' => 1,
                     'application_id' => 'YOUR_APPLICATION_ID',
                     'api_key' => 'YOUR_ADMIN_API_KEY',
                      'search_key' => 'YOUR_SEARCH_ONLY_API_KEY',
                      'index_prefix' => 'magento2_' ] ];

Replace YOUR_APPLICATION_ID, YOUR_ADMIN_API_KEY, and YOUR_SEARCH_ONLY_API_KEY with the actual values from your Algolia dashboard (Admin > Algolia > Credentials).

If this resolves your issue, kindly click Kudos and Accept as a Solution.