Troubleshooting Scheduled Feeds Not Running Properly

If your scheduled feeds are not running as expected in Stock Sync, several common issues may be the cause. Below are the key checks and steps to resolve scheduling problems.

1. Check Feed Source Accessibility

A schedule may fail if Stock Sync cannot access the file. Common reasons:

• Incorrect file directory or missing file
• Permission issues preventing the app from reading the source
• Intermittent connection issues with your supplier’s server

Try manually running the feed. If the manual run also fails, the source file may be the issue.

2. Verify Credentials for FTP/SFTP/HTTP Sources

If you see errors such as incorrect username or password, the credentials may have changed without your awareness. In some cases suppliers update access settings.

Confirm your login details with your supplier if the schedule repeatedly fails.

3. Avoid Scheduling Conflicts

If two or more feeds are set to run at the exact same time, they may clash and cause delays because Stock Sync processes feeds in a queue.

To avoid conflicts:

• Space out feed start times at least 10-15 minutes so they do not run at the same minute.
• Consider using product filters to reduce processing time for large catalogs

4. Check for Stuck Feeds Blocking the Queue

A stuck feed can prevent other scheduled feeds from running. This can happen when:

• A feed is manually cancelled and restarted repeatedly
• A feed encounters an unexpected processing issue

If one feed is stuck, the following scheduled feeds may be delayed or skipped until the queue clears.

5. Confirm File Format Consistency

A feed may fail if the file structure changes unexpectedly between runs. For example:

• Row separator/encoding changes
• Supplier modifies the file export format

If a feed runs successfully one day and fails the next without any changes on your end, contact your supplier to confirm whether they altered the output format.

6. Ensure Unique Identifiers for Add Feeds

If an Add feed shows “0 products added,” this may be due to duplicate SKUs in the file. Add feeds require a unique identifier per product. If duplicates exist, the feed will skip those items.

To resolve this:

• Use a different field (such as Stock Code) as the unique identifier
• Or combine multiple columns to create a unique SKU

7. Check Activity Logs When Unsure

If a schedule did not run:

• Confirm if another feed was already processing
• Check for delays caused by earlier feeds

While full logs may not always be visible, timestamps in the Activity Log can help determine sequence and cause.

Summary

If your scheduled feed fails to run:

• Confirm the file can be accessed
• Check credentials
• Ensure feeds are not scheduled at the exact same time
• Look for stuck feeds blocking the queue
• Verify the file format hasn’t changed
• Ensure unique identifiers for Add feeds

If none of the above resolves your issue, contact support with:

• Feed name
• Approximate run time
• Any error messages shown

This will help the team investigate backend logs and identify the root cause.

Updated on: 20/05/2026