Tasks by PublishPress Future (the modern evolution of Post Expirator) lets editors schedule arbitrary actions against a post: change status, draft, unpublish, move to category, run a hook. Each task writes the chosen action and its arguments into the publishpress_future_action and publishpress_future_action_args post meta keys, and the actual job is queued in WordPress through Action Scheduler under the publishpress_future_run_workflow hook stored in wp_actionscheduler_actions.

SleekView Charts reads both ends. A Number KPI counts pending tasks across the site. A Pie groups them by the action stored in publishpress_future_action: unpublish, draft, trash, change-status, change-category. A Bar splits tasks by post_type joined from wp_posts, useful when posts, products, and events all queue tasks. An Area trends tasks per day from the Action Scheduler scheduled_date_gmt column so the editorial calendar lines up with the queue.

Because the data lives in postmeta and the Action Scheduler table, the dashboard reads it natively without an extra log. Past executions, queued tasks, and per-action mix all appear on the same screen, refresh on every render, and travel into editorial reviews instead of staying buried behind a per-post sidebar.

Tasks by PublishPress Future is the workflow successor to the long-running Post Expirator and powers per-post automation across a large slice of WordPress sites. The plugin does its job well, but once tasks are scheduled the queue goes quiet. Editors never see how many posts will run an automation next week, ops never sees failed jobs that need a retry, agencies never report on workflow reliability.

The data exists the whole time, split across the publishpress_future_action meta and the Action Scheduler table, but no admin screen joins them. SleekView Charts reads both, exposes them as one data source, and turns the queue into a dashboard. Pending tasks, action mix, post-type split, and daily execution trend all live on one screen.

Failed tasks get their own card. The editorial calendar gains a queue view, ops gains an alert path, and agencies gain proof that the automation is running on schedule.