Help, my feed won’t update or is stuck processing!

Sometimes a product feed may get stuck during the feed-generating process. This can happen for several reasons, and the root cause isn’t always obvious. Below are the most common issues and how to resolve them.

1. Schedule action failure

The plugin uses Action Scheduler to generate and process feeds. If a feed is stuck, it may be due to a failed scheduled action.

How to check:

1. Go to WP Admin → WooCommerce → Status → Scheduled Actions.
2. Under the In Progress tab, see if there’s a feed action running.
3. If not, check the Failed tab.
4. Look for an event with the hook adt_pfp_as_generate_product_feed_batch that matches your stuck feed ID.

If you find an error like below:

• It often indicates your server’s max_execution_time is too low (less than 300 seconds).
• Increase it in your hosting configuration (your hosting provider can help).

Product Feed Pro includes a Regenerate Action Schedulers tool that re-creates the scheduled refresh task for every active feed, which is exactly what you need when you find a stuck or missing action above. Go to Product Feed → Settings → General, scroll to Other settings, and click Regenerate Action Schedulers. This re-creates the refresh schedule for feeds set to hourly, twice daily, or daily and, if you’re on Product Feed Elite, for feeds with a custom refresh interval too. It doesn’t change any feed data or configuration.

2. Automatic feed generation paused

This applies to Product Feed Pro 13.5.7 and newer.

Starting in Product Feed Pro 13.5.7, adaptive batch sizing keeps track of crashed generation runs automatically. If a feed’s scheduled generation crashes three times in a row, the plugin pauses that feed’s schedule and shows this notice on the plugin’s own admin pages:

Product Feed Pro: automatic feed generation paused. Generation of the following feed(s) crashed repeatedly, usually because the server ran out of memory or execution time: [feed names]. Scheduled generation is paused for these feeds. To retry, refresh the feed manually. A successful run resumes the schedule automatically. If it keeps failing, ask your host to raise the PHP memory limit or set a smaller fixed batch size in the plugin settings.

A few things worth knowing about this notice:

• A manual refresh always runs, even while a feed is paused. Only the automatic schedule is blocked.
• One successful run resumes the schedule and clears the notice by itself. There’s no button to reset it.
• Cancelling a feed run doesn’t count as a crash.
• A data or logic error puts the feed into the Error status instead of triggering this pause, since that isn’t a server-resource problem.

To resolve it:

1. Refresh the feed manually and see if it completes.
2. If it fails again, go to WooCommerce → Status → Logs and open the log with source woo-product-feed-pro. It records the plugin’s batch-size decisions and crash recovery.
3. Ask your host to raise the PHP memory limit or max_execution_time.
4. If it still won’t complete, set a smaller fixed batch size in the plugin settings. Keep in mind this turns off adaptive batch sizing for that feed. For detailed instructions, see Batch size configuration product feed.

3. Batch size

If you’re seeing timeout errors (like the one shown above), your server may be struggling to process too many products at once. This often happens when the default batch size is set higher than your server’s available resources can handle.

To resolve this, try reducing the batch size in the Product Feed plugin settings. A smaller batch size lowers the server load during feed generation and helps prevent the process from getting stuck.

Follow this step-by-step guide to learn how to adjust the batch size in the plugin.

4. Theme/plugin conflict

Conflicts with other themes or plugins are a common cause of stuck feeds.

Plugin conflict test:

1. Deactivate all plugins except Product Feed Pro, Product Feed Elite (if installed), and WooCommerce.
2. Check if the issue is resolved.
3. If yes, reactivate plugins one by one and test after each activation to find the conflicting plugin.

Theme conflict test:

1. Switch to a default theme (e.g., Twenty Twenty or Storefront).
2. Check if the feed processes correctly.

If you find a conflict, contact our support team with the details.

Theme or plugin conflicts may also trigger fatal errors. If that happens, see the section below.

5. Fatal errors

A fatal error may stop the feed process.

How to check:

1. Go to WP Admin → WooCommerce → Status → Logs.
2. Open the latest fatal-errors log.
3. Look for entries related to woo-product-feed-pro or woo-product-feed-elite.

If you find an error, share the log with our support team.

By following these steps, you can usually determine if the issue is related to hosting limits, batch size, or conflicts with other plugins or themes.

6. Disable HTTP feed generation requests

If your feed keeps getting stuck or doesn’t complete properly, it might help to switch how the feed is generated. The plugin includes an option called “Disable HTTP feed generation requests” that changes the way feed processing works.

When enabled, this option forces feed generation to happen entirely on the server side rather than being triggered by your browser. This can prevent timeouts or incomplete feeds, especially on larger stores or slower hosting environments.

To enable it:

1. Go to Product Feed → Settings → General.
2. Find the option “Disable HTTP feed generation requests”.
3. Check the box to activate it, then save your settings.

You can learn more about what this option does and when to use it here: What Does “Disable HTTP Feed Generation Requests” Do?

Issue not in the list

If none of the above fixes your issue, feel free to create a new ticket to reach out to our support team.

Please note that the ticket support system is exclusive to Product Feed ELITE users.

If you’re using only the Product Feed Pro plugin, feel free to open a new topic in the WordPress.org forum.