Troubleshooting scenarios for SaaS Data Export
This page describes behaviors you may observe when working with the SaaS Data Export that are typically caused by misconfiguration or misinterpretation of sync results. Use the descriptions below to identify the root cause and apply the appropriate resolution.
Configurable or bundle product missing in Commerce services configurable-bundle-missing
Issue: A configurable or bundle product has Enabled status in Adobe Commerce but is either not returned in the storefront or displays with a Disabled status in Commerce SaaS services.
Cause: The effective status of composite products depends on the status of their child products, not just the parent product status. Commerce SaaS services reflect this computed status:
- Configurable products - at least one product variant must be enabled.
- Bundle products - at least one product must be enabled for each required bundle option.
If these conditions are not met, the parent product is treated as disabled even if its own status is set to Enabled.
Solution:
- For configurable products, verify that at least one associated simple product variant is enabled and assigned to the correct website and store view.
- For bundle products, check that each required bundle option has at least one enabled child product. A required option with all disabled children causes the entire bundle to be treated as disabled.
- After enabling the appropriate child products, trigger a resync or wait for the next scheduled sync, then confirm the updated status in Commerce SaaS services.
Prices not updated after catalog price rule activation prices-not-updated
Issue: After activating a catalog price rule using the Scheduled Update feature, prices are not updated. The commerce-data-export.log shows synced: 0 for prices feed after scheduled updates are applied.
Cause: A race condition can occur between cron groups when Scheduled Updates are used for catalog price rules. The catalog_data_exporter_product_prices indexer may run before its dependency, the catalogrule_product index, has finished rebuilding. As a result, the price exporter reads stale data and exports no changes.
Solution:
The immediate fix for this issue is a workaround: Configure both cron groups to run sequentially to eliminate the race condition:
-
Go to Stores > Configuration > Advanced > System > Cron (Scheduled Tasks).
-
Set Use Separate Process to No for both:
- Cron configuration options for group: index
- Cron configuration options for group: staging
-
Flush the configuration cache after saving.
Catalog data discrepancy between Adobe Commerce and connected services catalog-data-discrepancy
Issue: Product data shown in connected Commerce Services (such as Live Search or Product Recommendations) does not match the catalog data in Adobe Commerce. For example, a product name, price, or description appears outdated or incorrect on the storefront.
Cause: After a resync is triggered, it can take up to an hour for the data to update and be reflected in UI components. If the discrepancy persists beyond that window, the item may not have been picked up by the last sync, or the sync did not detect a change because the feed data was already marked as up to date.
Solution:
- From the Commerce storefront, open the search results. Then, select the product in question to open its detailed view.
- Copy the JSON output and verify that it matches what you have in the Commerce catalog.
- If the content does not match, make a minor edit to the product in your catalog, such as adding a space or a period, to force the change to be detected.
- Wait for a resync or trigger a manual resync from the CLI or the Data Feed Sync Status page in the Admin.
For additional troubleshooting of catalog data in Product Recommendations, see Troubleshoot the Product Recommendations module in the Commerce Knowledge Base.
Data sync is not running on schedule sync-not-on-schedule
Issue: The data sync does not run on schedule, or no items are being synced despite product changes in Adobe Commerce.
Cause: The most common causes are cron jobs not running or indexers not configured in Update by Schedule mode.
Solution:
- Confirm that cron jobs are running.
- Verify that the indexers for the following feeds are set to Update by Schedule: Catalog Attributes, Product, Product Overrides, and Product Variant. Check from Index Management in the Commerce Admin or using the CLI:
bin/magento indexer:show-mode | grep -i feed.
Catalog sync has a Failed status catalog-sync-failed
Issue: The catalog sync shows a Failed status on the Data Feed Sync Status page.
Cause: An unrecoverable error occurred during the data collection or submission phase. Common causes include API authentication issues, network errors, or data validation failures.
Solution:
-
Review the data export error logs for details on the failure. See Review logs and troubleshoot for log format and extended logging options:
var/log/commerce-data-export-errors.logfor errors during data collection.var/log/saas-export-errors.logfor errors during data submission.
-
If the error is not related to configuration or a third-party extension, submit a support ticket with the relevant log entries.
Log shows “operation skipped - process locked” messages process-locked
Issue: The commerce-data-export.log file contains entries similar to the following:
{"feed":"products","operation":"partial sync","status":"operation skipped - process locked by \"full sync(1234)\"", ...}
Cause: This is expected behavior, not an error. The message appears when a cron-triggered partial sync attempts to run while a full reindex or saas:resync is already in progress. The SaaS Data Export extension uses a feed lock mechanism to prevent conflicting concurrent sync operations.
Solution:
No action is required. Once the running process completes and releases the lock, the next cron execution picks up and syncs any pending changes. For details on how the lock mechanism works, see Feed lock mechanism for SaaS Data Export.