The Job.update_moregreetings job was runned with max_time=240 timeout. After several execution the whole DB was updated, I've got the "Done." message. Further calls to the job returned "Job already running".
After inspection, the moregreetings_job_status is still "busy" in civicrm_setting, thus preventing running the job again.
In my understanding the job doesn't updates the status to "0" (last_id when finishing normally), just when it didn't finished yet.
The
Job.update_moregreetingsjob was runned withmax_time=240timeout. After several execution the whole DB was updated, I've got the "Done." message. Further calls to the job returned "Job already running".After inspection, the
moregreetings_job_statusis still "busy" incivicrm_setting, thus preventing running the job again. In my understanding the job doesn't updates the status to"0"(last_id when finishing normally), just when it didn't finished yet.This could be related to #14