PublishPress Future Pro schedules each post's expiration or status change as a row of postmeta (_expiration-date, expirationdate_status, expirationdate_options) plus a job in wp_actionscheduler_actions. The default Future Actions screen sorts on date and post type, which works fine for a small content library and gets thin once a site has hundreds of scheduled actions across post types.

SleekView joins the postmeta keys to wp_posts and to wp_actionscheduler_actions so target post title, scheduled action (draft, trash, stick, change category), scheduled date, and Action Scheduler status are all first-class columns. Filter to actions due in the next 24 hours, sort by post type, or pin a saved view of failed actions for retry.

Inline edits route through PublishPress Future's own helpers, so changing the scheduled date or action calls the same code path the post-edit screen uses. Action Scheduler entries update accordingly, so there is never a stale row between the two systems.

Scheduled actions are easy to set and easy to forget. A marketing manager schedules a campaign banner to trash itself on a specific date, a knowledge-base editor schedules an old article to move to draft, an admin schedules a bulk category change for the end of the quarter. Each of those entries lives in wp_postmeta with a matching Action Scheduler row, but the default UI shows them as a flat list with limited filters, which means surprises happen.

A campaign extends, but the trash action runs anyway. An article moves to draft on the wrong date. A failed run sits unnoticed for a week.

A real grid changes the picture. Filter to the next 24 hours and you see exactly what is about to fire. Filter to failures and you see exactly what needs a retry.

Bulk reschedule turns a campaign extension into a five-minute task. The data has been there all along; the working surface is the part that was missing.