Yes. SleekView reads synced task rows from inside WordPress, so the EasyCron WordPress connector that syncs tasks into the WordPress database is required. The connector also handles the EasyCron API calls that fire when a card is dragged between lanes, which keeps the kanban integrated.

Yes. The drag handler calls the EasyCron API through the connector, which pauses the schedule on the EasyCron service. The card status in WordPress matches what the EasyCron service shows, so there is no risk of the kanban drifting from the actual external schedule state.

Yes. The EasyCron connector keeps a rolling window of task run history, and SleekView reads whatever sits inside that window. A common pattern is to keep two weeks of history, which is plenty for monitoring and for an incident review to walk back through recent cron activity.

Yes. SleekView views are configuration only, so you can build one board filtered to production tasks and another to staging tasks from the same synced EasyCron task list. Each admin picks a default board, and lead admins pin shared boards into the sidebar for the team.

SleekView reads the task status column on every page load, so a new status value shows up as its own lane at the end of the board. You can drag it into the right position, assign a color, and decide which fields the lane cards should surface without writing any code.

Each failing card opens a side panel showing the full last HTTP response body, the response headers, the response code, the cron expression, the target URL, and the next scheduled run timestamp. Admins triage the failure inside the kanban without opening EasyCron.

Yes. SleekView respects WordPress capabilities, so you can require a senior admin capability before a card lands in the disabled lane for production-tagged tasks. Junior engineers pause staging tasks freely, but only seniors flip the production cron schedule from the kanban.

SleekView reads and writes the existing EasyCron connector synced task table without adding shadow tables for EasyCron data. View configuration sits in its own small options row, so uninstalling SleekView leaves every synced task, status, and audit row exactly where the connector wrote them.