CiviCRM Community Forums (archive)

Hi,

On a site that we've just upgraded from 3.3.5 to 3.4.3, there was a mailing that was created before the upgrade and scheduled to send at a time after the upgrade. This has failed to send: its status stayed 'Scheduled' and no child job was created.

I tracked down one problem: the queries in Mailing/BAO/Job.php runJobs, runJobs_pre and runJobs_post now include domain_id, which wasn't set on mailings created before the upgrade. I set this field for the scheduled mailing and ran civimail.cronjob.php again. The mailing now moved to 'Running' and a child job was created, but no mails were sent.

I've looked at the query being run at the start of deliver(), this returns no results because civicrm_mailing_event_queue has no records for the relevant job_id. So the next stage would be to work out why that is. There seem to be several changes to Mailing/BAO/Job.php . Would it be best to cancel the mailing & create a new one based on it?

Dave J

Hi Deepak,

Ah, I didn't find that issue, thanks!

Dave J