Troubleshooting Scheduling Issues with Automated Feeds

This guide covers common reasons why automated feed schedules may fail, run late, or remain stuck in Queuing mode. Use the steps below to diagnose and resolve scheduling issues.

1. Check for File Directory or Permission Issues

If a scheduled feed does not run but works manually, the issue may be related to file access.

Common causes include:

• Incorrect file directory paths
• Missing or inaccessible files
• Permission restrictions on the server

Try running the feed manually. If it succeeds, review the source file location and ensure the app has access.

2. Verify FTP Credentials

Feeds that rely on FTP sources can fail when authentication details are incorrect.

If you see repeated errors such as incorrect username or password:

• Confirm the credentials with your supplier or hosting provider
• Test the credentials in an FTP client (such as FileZilla)
• Ensure files have not been removed or renamed on the server

3. Avoid Scheduling Conflicts

Feeds scheduled to run at the same minute may conflict due to queue processing.

To prevent delays:

• Space out feed schedules so they do not start at the exact same time
• Apply Store Product Filters to reduce processing time when scanning large product catalogs

4. Understand Queuing Behavior

A feed may show "Queuing" if:

• The previous scheduled run has not completed
• The next allowed run time has not yet been reached based on the plan’s update frequency

For example, on a plan that updates once every 24 hours, incoming files received before the next scheduled run will remain queued until the cycle resets.

You can review the Activity Log to confirm the last completed update and the next run time.

5. Plan Limitations

Some plans only allow a limited number of active feeds. If the plan allows only one active automated feed, ensure that:

• Only one Update Feed is enabled
• All other Update Feeds are deleted or disabled to prevent conflicts

6. System-Wide Delays

On rare occasions, processing delays may occur due to high load. In these cases feeds may:

• Remain in Queuing longer than usual
• Take unusually long to finish

If delays persist, share specific feed names with support to investigate.

7. When All Else Fails

If a feed appears stuck or fails repeatedly:

• Cancel the current run
• Restart the feed manually
• Confirm the feed's configuration (source file, schedule, filters, and credentials)

If the issue continues, contact support with:

• The feed name(s)
• The time the feed was scheduled to run
• Any error messages shown

These steps will help identify and resolve most scheduling issues with automated feeds.

Updated on: 10/06/2026