i had it working fine on another server - had to disable it and re-enable it in a process to move ctools and entity api from modules to sites/all/modules - and now all it does is fall behind schedule - it is not running any jobs at all
If I run them manually - more just fal behind
I tried background process and had to change back to serial
cron debug the module does nothing but bring up the ultimate cron queue page
**** EDIT ****
Do not know what i did but - all the date launch job dates all have changed from the old date it was originally installed on the old server - to now today's date
BUT STILL - it appears is not running any jobs they just get behind
Comments
Comment #2
bobburns CreditAttribution: bobburns commentedComment #3
bobburns CreditAttribution: bobburns commentedA mix in terminology - is always bad. What is called "automated cron" for Drupal 7 - is actually poormans cron integrated into Drupal 7 ( https://www.drupal.org/project/poormanscron ) where on that page it says " #D7CX: We don't need to pledge that Poormanscron will have a full Drupal 7 release on the day that Drupal 7 is released because Poormanscron is part of Drupal 7! referring to https://www.drupal.org/node/331611 and at https://www.drupal.org/docs/7/setting-up-cron/overview "poormans cron" is then referred to as "automated cron" but at admin/config/system/cron especially if one is using Ultimate Cron - it is buried at admin/config/system/cron/settings/poorman - and if it is disabled "somehow" which is NOT supposed to be the default - Ultimate Cron will not run. Selecting either Background Process or Serial - then turns Drupals internal cron back on in an "automated fashion" caused by page visits and Ultimate Cron will launch the queued scheduled jobs and will report in the Status page running normally
Comment #4
bobburns CreditAttribution: bobburns commented