Live search catalog not synchronized
This article provides solutions for the Adobe Commerce issue where your catalog data is not synchronized correctly when using the Live Search extension.
Affected products and versions
- Adobe Commerce 2.4.x with Live Search extension installed
Issue
Your catalog data is not synchronized correctly, or a new product was added but does not appear in search results.
catalog_data_exporter_products
and catalog_data_exporter_product_attributes
are now called cde_products_feed
and cde_product_attributes_feed
as of Live Search version 4.2.1. For merchants on versions prior to 4.2.1, look for the data in the old table names, catalog_data_exporter_products
and catalog_data_exporter_product_attributes
.Steps to reproduce
- Configure and connect Live Search for your Adobe Commerce instance as described in Install Live Search > Configure API keys in our user documentation.
- After 30 minutes, verify the exported catalog data as described in Install Live Search > Verify export in our user documentation.
- After 30 minutes, test the connection as described in Install Live Search > Test the connection in our user documentation.
Or
- Add a new product to the catalog.
- Try running a search query using the product name or other searchable attributes after 15-20 minutes from the time Magento indexer + cron have run to sync data to backend service.
Expected result
- Exported catalog data can be verified
- Connection is successful
- New product appears in search results.
Actual result
Exported catalog cannot be verified and/or connection is not established because the API key has changed.
Solution
There are several things you might do to try and fix the catalog syncing issues.
Wait for changes to be applied
Once you configure and connect, it can take over 30 minutes for the index in ES (Elasticsearch) to be created and search results to be returned. Subsequent one-off product updates are expected to be indexed within a few minutes.
Sync product data for a specific SKU
If your product data is not synced correctly for a specific SKU, do the following:
-
Use the following SQL query and verify that you have the data you expect in the
feed_data
column. Also, make a note of themodified_at
timestamp.code language-sql select * from cde_products_feed where sku = '<your_sku>' and store_view_code = '<your_ store_view_code>';
-
If you do not see the correct data, try to reindex using the following command and rerun the SQL query in step 1 to verify the data:
code language-bash bin/magento indexer:reindex cde_products_feed
-
If you still do not see the correct data, create a Support ticket.
Check timestamp of last product export
-
If you see the correct data in
cde_products_feed
, use the following SQL query to check the timestamp of the last export. It should be after themodified_at
timestamp:code language-sql select * from scopes_website_data_exporter;
-
If the timestamp is older, you can either wait for the next cron run or trigger it yourself using the following command:
code language-bash bin/magento cron:run --group=saas_data_exporter
-
Wait for
<>
time (time for incremental updates). If you still do not see your data, create a Support ticket.
Sync specific attribute code
If your product attribute data isn’t synced correctly for a specific attribute code, do the following:
-
Use the following SQL query and verify that you have the data you expect in the
feed_data
column. Also, make a note of themodified_at
timestamp.code language-sql select * from cde_product_attributes_feed where json_extract(feed_data, '$.attributeCode') = '<your_attribute_code>' and store_view_code = '<your_ store_view_code>';
-
If you do not see the correct data, use the following command to reindex and then rerun the SQL query in step 1 to verify the data.
code language-bash bin/magento indexer:reindex cde_product_attributes_feed
-
If you still do not see the correct data, create a Support ticket.
Check timestamp of last product attribute export
If you see the correct data in cde_product_attributes_feed
:
-
Use the following SQL query to check the timestamp of the last export. It should be after the
modified_at
timestamp.code language-sql select * from scopes_website_data_exporter;
-
If the timestamp is older, you can either wait for the next cron run or trigger it yourself using the following command:
code language-bash bin/magento cron:run --group=saas_data_exporter
-
Wait for 15-20 minutes (time for incremental updates). If you still do not see your data, please create a Support ticket.
Sync after API configuration change
(Known issue) If you have changed your API configuration, which results in a change in your Data Space ID and find that your catalog changes are no longer syncing, run the following commands:
bin/magento saas:resync --feed products
bin/magento saas:resync --feed productattributes
Related reading
- Onboard Live Search in our user documentation
- Review logs and troubleshoot Adobe Commerce SaaS data export and synchronization in Adobe Commerce SaaS Data Export Guide
- Best practices for modifying database tables in the Commerce Implementation Playbook