Hi @erikmolenaar ,
Sorry to hear about your issues with the Pinterest For WooCommerce extension. Action scheduler overload and database bloat aren’t typical with our extension and are unique to your store instance.
I reviewed your profile and any support threads you created, and couldn’t find any topics where you requested help with Pinterest for WooCommerce. It’s unclear why you call it “badly designed,” as you haven’t requested help in the forums. Documentation for the extension is available here.
Could you please create a new support thread so we can assist you further? Thanks.
Ok fair enough to elaborate:
As it stands, the feed generation job is not robust at scale: it uses an immediate, self-chaining Action Scheduler pattern (chain_batch) but mutates its cursor (feed_last_queued_item_id / last_batch_id) in get_items_for_batch() (src/FeedGenerator.php:369) before the batch is actually processed, and then handle_unexpected_shutdown() (line ~192) blindly reschedules timed-out batches without any deduplication, so a timeout can create overlapping retries that fetch different work than originally intended and “fan out” into many more batches than necessary. On top of that, the is_running() guard is weak (it only checks the next scheduled action, not the full queue), there’s no circuit breaker/max-batch cap, and the batch source query vs. product filtering can produce empty/low-yield batches that still advance state. Together these are classic ingredients for runaway scheduling, huge volumes of completed actions, and database bloat/timeouts in Action Scheduler cleanup.
Thanks for sharing your concerns. I’ve shared them with the dev team. While we don’t troubleshoot issue in the review section, please feel free to create a new support thread so we can assist you further.
