How to Troubleshoot Issues with the Sync Process

If you are experiencing problems with the sync process in Stock Sync, here are the key steps and scenarios to help you troubleshoot effectively.

When the Sync Queue Says “Multiple Feeds Are Running”

If a sync remains incomplete and displays “Multiple feed are running. Please wait a few minutes for it to restart”, another feed may still be processing or a previous job may be stuck. Stock Sync processes feeds in a queue, so later syncs can be delayed until the active job finishes.

• Check the feed's status and activity logs for a running or stalled process.
• Wait a few minutes for the queue to clear before starting another sync.
• If the job remains stuck, cancel the process and click Force Start / Start Process to restart it.
• Avoid repeatedly cancelling and restarting feeds, as this can contribute to queue conflicts.
• If several feeds remain blocked, provide the feed name or ID and the exact queue message when requesting an investigation.

When a Sync Has Not Completed for Several Days

If the queue message remains for days rather than clearing after a few minutes:

1. Open the feed and review its status and activity logs.
2. Check whether another feed is still running or the job is stalled.
3. Cancel the stuck process, then click Force Start / Start Process once to restart it.
4. If it still does not complete, provide the feed name or ID and the exact queue message for investigation.

Do not repeatedly cancel and restart the feed, because this can add to queue conflicts.

When the Sync Result Is "0 Updated"

A sync showing "0 updated" does not always mean there is an error. It can happen when no product data has changed since the previous sync.

However, if you expected updates:

• Check your field mapping to ensure the correct columns are linked.
• Review filters to confirm they are not excluding items unintentionally.
• Stock Sync does not send notifications for zero-update results, so checking the Sync Logs is recommended.

When the Sync Cannot Connect or Fails Unexpectedly

If your sync cannot connect to the supplier or server:

• Confirm the connection type being used.
• Verify with your supplier if anything changed on their side, including feed URLs, endpoints, credentials, or file availability. Stock Sync can only sync using the URLs, endpoints, and credentials provided by the supplier.
• If you edited DNS records or moved your domain to another platform, validate that the store’s endpoints and feed URLs still resolve correctly. DNS or platform changes can affect the connection even when the feed format has not changed.
• If the supplier confirms the feed is available, check the Sync Logs and run a Preview Sync to verify that the expected products and quantities are detected. A Preview Sync does not update your store; use Start Process for the actual sync.
• Some issues may resolve from the supplier's side without changes within Stock Sync. If the feed starts working again, no Stock Sync change may have been required.
• If the sync fails intermittently with errors like "file not exist", check whether your supplier overwrites the feed file on a schedule. A timing collision can occur if the sync runs while the file is being replaced; ask the supplier when the upload finishes and adjust the sync schedule (for example, to every 1:20 or 1:30) so the file is fully uploaded before Stock Sync retrieves it.
• Keep the feed's product identifiers consistent. Use an identifier that matches exactly in both the source and destination; SKU is precise only when the supplier provides the same SKU values. If variant sizes are stored in different option fields, use the corresponding Handle + Option mapping or create a separate update feed for the affected variant layout.
• After changing identifier or feed settings, run a preview sync and monitor the next automated syncs. Preview Sync verifies which products and quantities are detected but does not update the store; use Start Process for the actual update.

When the Schedule Stops Running

If your automated sync suddenly stops:

• Ensure the automation is still enabled.
• In certain periods, internal system issues may have caused WooCommerce schedules to pause—these have been fixed.
• If no failure notification was received, it may have been due to a past system-level routing issue. Notification handling has since been patched.

When You Need to Run Sync Manually

• You can run a sync anytime by clicking Start Process.
• Preview sync does not update your store; only real sync does.
• On the Free plan, syncs must be triggered manually.

When Sync Seems Slow or Not Instant

Some changes require a few minutes to process and appear store-side. If unsure, check the Sync Logs or test a single SKU.

When Using Two-Way Sync

Stock Sync supports two-way syncing, but requires:

• One Update feed (e.g., Google Sheets → Shopify)
• One Export feed (e.g., Shopify → Google Sheets)

These must not run at the same time to avoid conflicts.

When Metafields Cause Sync Issues

If you recently changed metafields:

• Cached metafield types may cause errors.
• Removing and re-adding the feed can refresh these definitions.

When Products Are Missing or Filtered Out

If many products show as "not found":

• Check your filters; disable them temporarily.
• Review whether variants are excluded by quantity-based or tracking-based filters.
• Ensure your source file actually contains the missing SKUs.

When Sync Does Not Update Due to Store Restrictions

For WooCommerce:

• Stock Sync uses the WooCommerce REST API.
• If using plugins that restrict access (e.g., password-protected categories), ensure the plugin allows access through REST API.

If issues persist after these steps, contact support with:

• A sample SKU
• Current feed name
• A screenshot of mapping and filters

This helps us diagnose the issue quickly and accurately.

Updated on: 03/08/2026