Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Overdue WP CRON can lead to incorrect "next run" time indicator #92

alexkingorg opened this Issue Jun 18, 2012 · 2 comments


None yet
2 participants

alexkingorg commented Jun 18, 2012

Looks like some combination of things (like an overdue WP Cron job) can lead it to show as next run in "go", which is odd.


jondavidjohn commented Sep 4, 2012

Looks like this is caused by a missing type specifier in this sprintf call that handles fuzzy dates in the past tense.


Do we want to handle the next_run indicator differently?

"Next automatic run a couple of hours ago" vs "Next automatic run missed. Please re-run manually."


jondavidjohn commented Sep 12, 2012

Fixed with 28bcd92

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment