[PaaS only]{class="badge informative" title="Applies to Adobe Commerce on Cloud projects (Adobe-managed PaaS infrastructure) and on-premises projects only."}

Data Feed Status Monitoring

Adobe Commerce administrators can monitor the synchronization status of data exported from Adobe Commerce to connected Commerce services using the Data Feed Sync Status page in the Commerce Admin.

Data Feed Sync Status detail page with feed item status reporting

This page provides real-time insights into the health and performance of data export feeds that transfer product and category data from Commerce to external services such as Product Recommendations, Live Search, and Catalog Service.

The sync status page shows only the export status. A success status indicates that the data is successfully exported to SaaS database for publication. Use the Data management dashboard to track data transferred from the Commerce database to connected services.

Monitoring feed status helps ensure data consistency and enables prompt resolution of any issues that arise during the export process. Administrators can:

  • View the synchronization status for all data feeds
  • Identify and troubleshoot errors in feed processing
  • Access detailed status information for individual feed items

Status is tracked for the following feeds:

  • Products Feed
  • Product Attributes Feed
  • Categories Feed
  • Product Overrides Feed
  • Product Prices Feed
  • Product Variants Feed
TIP
To learn more about the data synchronization process, see Synchronize data with SaaS data exportin the SaaS Data Export Guide*.

Install the extension

The Data Feed Status page is available to all Commerce merchants with active licenses for the following Commerce services:

Requirements

Installation steps

Add the adobe-commerce/module-data-exporter-status module using Composer:

composer require magento/module-data-exporter-status

For detailed installation steps, see the following guides:

Access the Data Feed Status page

From the Commerce Admin, Access the Data Feed Status page from the Commerce Admin at System > Data Transfer > Data Feed SyncStatus.

Data Feed Sync Status page summarizing data feed export activity

Data Feed Status monitoring provides two interfaces:

Data Feed Sync Status summary

The Feed Sync Status summary page provides information about data feed export activity including the following information:

Field
Description
Feed Name
The name of the feed indexer responsible for synchronizing a specific entity or its part, for example product or product price.
Source Records
Number of records available for export from the Commerce database. This number can be larger than the number of records displayed in the Commerce Admin as each feed item belongs to a specific scope, such as Store View code.
Successfully Sent Records
Number of records successfully transmitted to Commerce SaaS for further processing. If errors occurred during transmission, the number of records successfully transmitted to external services.
Failed Records
Number of records that failed to export and require attention.
Action
Select Details to view the sync activity for a feed.

Data Feed Sync Status Details

From the Data Feed Status summary page, click a feed name or use the View Details action to access detailed information about individual records within a feed.

Data Feed Sync Status - Details page with feed item status reporting

The detail view provides the following information for each feed item:

Field
Description
Feed Item ID
Internal identifier for the feed record
Entity ID
The source entity ID (product ID, category ID, and so on)
Export Status
The synchronization status of the feed item. Current status of the export attempt with color-coded indicators
Last Sync Date
Timestamp when the record was last sent to Commerce Services
Is entity deleted?
Indicates whether the entity or its part (product or product price for example) has been deleted in Adobe Commerce. Items are displayed only if an error occurred during synchronization.
Request ID
A unique identifier for the synchronization request. Provide this ID to Support when troubleshooting specific entity updates.
Error
Detailed error information if the feed item failed to synchronize.

You can manage the view using the following controls:

  • Mass Action to schedule resync for selected feed items
  • Filters
  • Default View to create and save a filtered view, and switch between views
  • Columns to show and hide columns in the table.

Feed health indicators

At the top of each feed detail page, critical health indicators provide system status for each feed:

Indexer status

  • Valid: Data is synchronized; no reindex required.
  • Invalid: Original data was changed; the index should be updated.
  • Processing: Indexing in progress.
TIP
To learn more about index processing, see the Index Management topic.

Changelog backlog

  • All synced: No pending changes to process
  • Items in backlog: Number of pending changes waiting to be processed

Export status types

The system provides status indicators to help you quickly identify issues:

Status categories

Status
Description
Action required
Submitted to service
Feed item successfully exported to Commerce service.
None
Failed, will retry
Temporary failure. The system will automatically retry.
Monitor for resolution
Failed, requires attention
Failed due to application or data error.
Investigate and resolve the issue in the Error column
Awaiting submission
Queued for export but not yet processed.
Normal processing state

Monitor data feed status

When you update product and category related entities in the Commerce database, the data transfers to Commerce services according to your feed configuration. You can monitor this process in real time from the Data Feed Sync Status summary page.

IMPORTANT
The time it takes to complete data synchronization varies based on your catalog size, the volume of updated data, and external service performance.

When the number of successfully sent records matches the number of source records, it indicates that the sync is complete and all data has been transmitted successfully.

NOTE
Adobe also provides command-line interface tools and system logs that developers and system integrators can use to manage and track sync operations. For details, see the SaaS Data Export Guide.

Managing failed exports

To see the details of failed exports and take corrective action:

  1. From the Feed Sync Status page, find the feed with failed records.

  2. Click Details.

  3. Review error messages for specific failure reasons.

  4. Use mass actions to schedule resync operations for failed items.

Resync failed data

You can manually resync failed or problematic data feeds by using the Actions menu on the Data Feed Sync Status - Details page.

While the system automatically retries certain types of failures, manual intervention may be necessary in the following scenarios:

  • You notice authentication or permission errors (401, 403 status codes).
  • After resolving data format issues that caused payload errors.
  • Following updates to external service configurations or endpoints.
  • You are deploying customizations that impact data export processes.

By proactively monitoring feed status and addressing failures promptly, you can maintain data consistency and reliability across your Commerce ecosystem.

Manually resync feed items

If you need to resync specific feed items:

  1. Select Records: Use checkboxes to select failed records that need attention.
  2. Choose Action: Select Schedule Resync from the mass action dropdown.
  3. Confirm: Click Submit and confirm the resync operation.
  4. Monitor Results: Check the success message and monitor status changes.

Best practices

Regular monitoring

  1. Daily Checks: Review the overview page daily for any feeds showing high failure rates
  2. Weekly Deep Dive: Examine the detailed status for critical feeds (products, prices)
  3. Monthly Analysis: Track trends in export success rates and performance

Troubleshooting workflow

  1. Identify Issues: Look for errors and high failure counts
  2. Check Indexer Health: Ensure that indexers are valid and backlog is manageable
  3. Review Error Details: Click on failed records to see specific error messages
  4. Schedule Resync: Use mass actions to retry failed exports
  5. Monitor Resolution: Verify that resynchronized items show successful status

Fix common issues

High failure rates

Symptoms: Large number of records showing “Failed, require attention” status

Potential causes:

  • External service configuration changes
  • Data format incompatibilities
  • Authentication or permission issues

Resolution steps:

  1. Check external service status and configuration
  2. Review error messages for patterns
  3. Verify authentication credentials
  4. Contact external service support if needed

Slow export performance

Symptoms: High changelog backlog, slow status updates

Potential Causes:

  • Indexer performance issues
  • High data volume
  • External service rate limiting

Resolution Steps:

  1. Check indexer status and rerun if invalid
  2. Monitor external service response times
  3. Consider scheduling exports during off-peak hours
  4. Review system resources and performance

Authentication Failures

Symptoms: 401 or 403 status codes

Resolution Steps:

  1. Verify API credentials and tokens
  2. Check external service account permissions
  3. Renew expired authentication tokens
  4. Contact your service provider for access issues
recommendation-more-help
d3c62084-5181-43fb-bba6-1feb2fcc3ec1