Cron Scheduler

Fixed

• No index on Magento's cron_schedule any more. 1.0.0 added CRON_SCHEDULE_SCHEDULED_AT_STATUS; setup:upgrade now drops it. All queries filter on the job codes and statuses, so Magento's own index (job_code, status, scheduled_at) serves them, and every query has a lower time bound.
• Tasks › Delete with "Select All" deleted by loading every matching row. It now deletes in batches with SQL, with the grid's filters and keyword search, and keeps running tasks. Selected rows are deleted by their IDs, and only selections of the Tasks grid are accepted.
• Jobs › Last Run no longer scans the whole history: it shows the last run of the last 7 days, or "No run in 7 days". The same applies to techimprovement:cron:jobs.
• Email notifications: a job failing every minute could hide the problems of other jobs. Problems already handled are now left out by the query, and all new problems are read page by page. An email that could not be sent is tried again by the next checks (up to 5 times). Problems are recognised by run, job and scheduled time, so they are not mixed up when Magento reuses task IDs. Problems of excluded jobs are no longer read again at every check. Missed runs of the extension's queue job are not reported.
• Queue to Run Now: Magento could delete a queued run before it ran, because it did not match the job's schedule. Queued jobs are now kept in the extension's own queue and run within a minute by the job ti_cronscheduler_run_queued, with the same lock as Magento's cron. A job that is running already waits up to an hour. Jobs queued with 1.0.0 get the result of their task, or an error when the task is no longer in the cron schedule.
• Run in This Request: the admin session is released before the job runs, so other admin pages of the same user no longer wait for the job. The result is shown above the job list. A run stopped by a PHP time limit, a fatal error or a killed process no longer stays "running": it is marked as an error with the next cron run.
• techimprovement:cron:run now starts the application like bin/magento cron:run (admin store, cron area and its configuration and translations).
• Disabled cron: when the cron is switched off in app/etc/env.php, jobs are no longer run or queued by hand, and the Jobs page and the dashboard say so.
• Disable / Enable: disabling a job marks its runs left "running" as errors (unless the job is running now). Enabling it removes the pending runs of the time it was disabled, which were reported as missed.
• Disabled jobs' history: the daily cleanup now applies the history settings of the job's cron group to disabled jobs, which Magento no longer cleans, and ends their runs stuck in "running" after a day.
• Daily cleanup: deletes at most 50,000 rows per run and kind (the next runs continue), with index-friendly queries, and runs with the queue job in the new cron group ti_cronscheduler, in its own process.
• Cron health: the time of the last cron run is read from the newest rows only and cached for a minute, as the admin notice asks on every page.
• Dashboard: "Running Now" counts in the database, and the running and overdue runs are read once per page.

New

• System › Cron Scheduler › Timeline: every cron run on a time axis, one row per job, colored and shaped by status and as long as the run took; ranges of 1 hour, 6 hours, 24 hours, 3 days or custom; zoom with buttons or Ctrl/⌘ and the mouse wheel; "Now" line and Go to Now; filters by job code, group and status; auto-refresh; details on hover and keyboard focus; keyboard navigation between runs; legend.
• System › Cron Scheduler › Tasks: grid of the cron schedule with status badges, durations, filters (including group and duration), keyword search in job codes and messages, saved views, CSV/Excel XML export, mass delete, newest first also for saved views without sorting, a cleanup of finished tasks older than a number of days, and a page per task with the full message.
• System › Cron Scheduler › Jobs: all jobs of all modules with group, class and method, module, default and effective schedule (changed here, from configuration, default or not scheduled), status, last and next run and errors of the last 24 hours; search, filters and sorting.
• Job actions, per job and for selected jobs: enable, disable (pending runs removed), edit schedule (validation, description and next 5 run times), reset to default, queue to run now, and run in the request (same lock as Magento's cron, recorded in the task list and in a run log with the admin username). Disabled jobs and changed schedules apply to Magento's cron, also for jobs whose schedule comes from the configuration.
• Email notifications about errors, missed runs and runs that take too long: one email per check, include and exclude lists with wildcards, a time filter per job, a history of reported problems. The email template is self-contained (no storefront header or footer) and shows the store name.
• System › Cron Scheduler › Dashboard: cron health from a heartbeat job with the crontab install commands when the cron has stopped, key figures and a chart of the last 24 hours, top failing, longest running and running jobs, pending backlog, missed jobs, jobs started by hand and recent notifications.
• Admin notice when the cron has not run for a configurable number of minutes.
• History cleanup: Magento's history settings per cron group shown in the settings, an optional daily deletion of finished runs older than N days, and the 90-day cleanup of the extension's own logs.
• Commands techimprovement:cron:jobs, techimprovement:cron:run and techimprovement:cron:clean.
• Role resources for the dashboard, timeline, tasks, deleting tasks, jobs, changing jobs, running jobs and the settings.