Both the free and the Pro versions of Advanced Cron Manager expose the same scheduled event store, and SleekView reads that store directly. The kanban renders the same way regardless of which version you run, and the Pro locking feature makes the running lane more accurate.

Yes. The drag handler calls the Advanced Cron Manager pause API, which writes the paused state to the event row in the wp-cron store. WordPress core checks that state on every tick, and the paused state causes wp-cron to skip the hook on the next scheduled run.

Yes. Dragging a card from the completed lane back to the due lane writes a new next run timestamp matching the current time, which causes the next wp-cron tick to fire the hook immediately. The original recurrence label is preserved, so the hook returns to its normal schedule.

Yes. SleekView views are configuration only, so you can build one board filtered to WooCommerce hooks and another to action scheduler queue hooks from the same wp-cron event store. Each sysadmin picks a default board, and lead admins pin shared boards.

SleekView reads the wp-cron event store on every page load, so a new hook shows up automatically as a card in the due lane with its own row. No board reconfiguration is required, and you can immediately filter the active lanes to that new hook to monitor it.

Each event card opens a side panel showing the full hook callback chain, the argument payload registered for the event, the recurrence label, the next run timestamp, and the last few completed run durations. Sysadmins can debug without leaving the kanban for the cron admin.

Yes. SleekView respects WordPress capabilities, so you can require a senior admin capability before a card lands in the paused lane for production-tagged hooks. Junior engineers can still pause staging hooks freely, but only seniors can pause a production hook on the live site.

SleekView reads and writes the existing Advanced Cron Manager schema without adding shadow tables for cron events. View configuration sits in its own small options row, so uninstalling SleekView leaves every wp-cron event and schedule exactly where the cron manager wrote them.