Clean expired transients and Action Scheduler logs in WooCommerce: a plugin you can build today

Transients are WordPress's temporary cache. A plugin stores a value for a set number of seconds, and WordPress saves two rows in wp_options: one with the value under the key _transient_X, and one with the expiry timestamp under _transient_timeout_X. When the transient expires, WordPress is supposed to delete it the next time that key is requested. Under load that cleanup step is skipped: the request that would have triggered it has something else to do, or no request ever reads the expired key again. The rows stay in the table indefinitely. On a busy WooCommerce store, tens of thousands of expired transient rows sitting there for months is not unusual.

Action Scheduler is the job queue built into WooCommerce. Every background task routes through it: order confirmation emails, subscription renewals, stock syncs, anything a plugin does not want to handle inline. Each task creates a row in wp_actionscheduler_actions. When the job completes the row is marked complete. When it fails the row is marked failed. These records are never removed unless something explicitly deletes them. On a store that has been running for a few years with active plugins, several hundred thousand rows in that table is ordinary, and most of them record jobs that finished long ago and will never be read again.

Expired transient rows are not autoloaded, so they do not add weight to every page request directly. What they do is bloat the wp_options table to the point where queries that scan it take longer. WordPress fetches all autoloaded options in a single query on every request. On a table with fifty thousand rows, that query is still navigating a large index even if it only returns two hundred rows.

The Action Scheduler problem is more direct. WooCommerce and its extensions query the actions table continuously to schedule and claim jobs. As the table grows past a few hundred thousand rows, those queries slow even with correct indexes in place. Admin pages that list scheduled actions, backup plugins that read the whole table, and cron runners firing at high frequency all become noticeably slower. The effect shows up most visibly in the WooCommerce dashboard and in WP-Cron status reports.

The plugin registers a daily WP-Cron event and runs two cleanup passes each time it fires. The first pass queries wp_options for any row whose name begins with transient_timeout and whose stored value is less than the current Unix timestamp. For each expired timeout row, it deletes that row and the matching transient row. Live transients are untouched; only rows past their expiry are removed.

The second pass reads a retention setting you configure on the admin page (default seven days) and collects all action IDs from wp_actionscheduler_actions where the status is complete, failed or canceled and the scheduled date is older than the threshold. It deletes the corresponding rows from wp_actionscheduler_logs first, then removes the action rows. Clearing the logs table first avoids orphaned records.

The admin page under WooCommerce > DB Cleanup shows three numbers: the current count of expired transient rows, the current count of eligible Action Scheduler records given the saved retention setting, and the time of the last cleanup run. A button runs the cleanup without waiting for the cron event. A number input lets you raise or lower the Action Scheduler retention period.

Deleting rows compacts the table logically but does not reclaim disk space or defragment indexes. To do that you run OPTIMIZE TABLE, which acquires a full table lock and can pause queries for several seconds on large tables. WP-Optimize and similar tools run that step during a low-traffic window. This plugin does not.

A separate performance drain this plugin ignores is autoloaded options that are large or should not be autoloaded. Some plugins store large serialized values under autoloaded keys, adding weight to every page request regardless of whether the value is used. Identifying those rows requires a tool that shows options by size and autoload status. This plugin has no such view.

Post revisions, trashed posts, spam comments, orphaned postmeta and session rows from third-party plugins are also outside scope. If any of those are contributing to the bloat, a general-purpose cleanup tool is the right call.

If you need to clean post revisions, trash, spam and orphaned postmeta in addition to transients and Action Scheduler records, WP-Optimize handles all of them in a scheduled sweep. If you want to run OPTIMIZE TABLE after each cleanup pass, WP-Optimize has a button for it. If you need to audit which options are autoloaded and how large they are, Advanced Database Cleaner breaks them down by row.

This plugin suits the store where expired transients and a swollen Action Scheduler table are the specific problem. It handles those two things, runs daily without configuration beyond the retention period, and adds nothing else to the stack. Paste the prompt below into Steem to build it. To add a per-run cleanup log and a weekly summary email, the follow-up is: Add a cleanup log to WC DB Cleanup: after each run, append a row to a custom table recording the date, expired transient count deleted and Action Scheduler count deleted. On the admin page, show the last ten runs in a table. Add a weekly summary email to the admin address with the totals for the past seven days.