Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • scheduled task invocation method selected by default isn't optimal
  • if user enabled "Run Scheduled Tasks from Cron" setting and don't add proper line (we don't show exact line anywhere) to crontab, then nothing would work (but user could think it works)

...

Solution

  1. write last time, when cron.php script was executed and it's execution method: web/cli;
  2. on scheduled task page:
    • ask user to enable scheduled task execution via cron (quick link, like with Change Logs section) if we know that cron is running;
    • if cron isn't running, then show exact crontab line, that user must add to it;
    • if cron is running, but it's interval is larger, then 1 minute (compare last recorded date with current execution date), then show warning, that it must be changed (on some hosting it's not allowed to run cron once per minute);
    • show last cron execution date (right now I need to look at all scheduled tasks and find out which one was executed last);
    • show relative scheduled task last/next run dates, e.g "5 min ago" or "in 10 hours", since it's easier to understand then comparing all scheduled task dates with current date (which even isn't shown on that page).
    • highlight "last run date" in red if scheduled task was late (was executed not in between 2 last execution intervals); this in most cases would indicate that cron is dead

Related Tasks

Jira Legacy
In-Portal Issue Tracker
serverSystem Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId513b375f-8291-3313-9d9f-704c39b1f915
keyINP-1182