Answers.Body: <p>I believe this is fixed with <a href="https://github.com/civicrm/civicrm-core/pull/15780" rel="nofollow noreferrer">https://github.com/civicrm/civicrm-core/pull/15780</a>. It will be hopefully included in a point release that should come out soon for 5.19</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-11-09T12:28:13.697Z
Answers.Text: That does solve my issue. Thanks.
Answers.UserDisplayName: Mark Westergaard
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-11-09T01:44:32.710Z
Answers.LastActivityDate: 2019-11-09T01:44:32.710Z
Answers.UserDisplayName: Seamus Lee
Body: <p>I upgraded to 5.19.0 and noticed that every report for completed mailings listed on the Find Mailings screen is now showing this message in the Delivery Summary section:</p>
  
  <pre><code>Delivery has not yet begun for this mailing. If the scheduled delivery date and time is past, ask the system administrator or technical support contact for your site to verify that the automated mailer task ('cron job') is running - and how frequently.
  </code></pre>
  
  <p>Despite this, the reports still show the Click-through Summary and other sections.</p>
  
  <p>I see this issue on both my production and development systems. I tried clearing cache. Other CiviMail reports (from the Reports tab) seem to be correct.</p>
  
  <p>CiviCRM 5.19.0<br>
  Wordpress 5.2.4<br>
  PHP 7.2.21<br>
  MySQL 5.7.23</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-11-08T05:34:57.343Z
Comments.Text: Sounds like it might be a bug. If you turn on "Enable Debugging" at Administer - System Settings - Debugging it might give more info since I think I see similar on the public demo but since it doesn't have real mail enabled I'm not sure. If you do see warnings when you turn that on I'd say you should report it at https://lab.civicrm.org/dev/mail/issues
Comments.UserDisplayName: Demerit
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-11-08T15:53:16.523Z
Comments.Text: See https://lab.civicrm.org/dev/mail/issues/56
Comments.UserDisplayName: Demerit
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-11-08T18:19:27.937Z
Comments.Text: Thanks, I followed up on https://lab.civicrm.org/dev/mail/issues/56.
Comments.UserDisplayName: Mark Westergaard
Tags: <wordpress><civimail>
Title: Issue with CiviMail reports after upgrade to 5.19.0
ThreadText: # Issue with CiviMail reports after upgrade to 5.19.0
  
  (Asked by: username_0 on 2019-11-08)
  
  I upgraded to 5.19.0 and noticed that every report for completed mailings listed on the Find Mailings screen is now showing this message in the Delivery Summary section:
  Delivery has not yet begun for this mailing. If the scheduled delivery date and time is past, ask the system administrator or technical support contact for your site to verify that the automated mailer task ('cron job') is running - and how frequently.
  
  Despite this, the reports still show the Click-through Summary and other sections.
  I see this issue on both my production and development systems. I tried clearing cache. Other CiviMail reports (from the Reports tab) seem to be correct.
  CiviCRM 5.19.0
  Wordpress 5.2.4
  PHP 7.2.21
  MySQL 5.7.23
  
  **Tags:** wordpress, civimail
  
  > **Comments:**
  > **username_1**: Sounds like it might be a bug. If you turn on "Enable Debugging" at Administer - System Settings - Debugging it might give more info since I think I see similar on the public demo but since it doesn't have real mail enabled I'm not sure. If you do see warnings when you turn that on I'd say you should report it at https://lab.civicrm.org/dev/mail/issues  
  > **username_1**: See https://lab.civicrm.org/dev/mail/issues/56  
  > **username_0**: Thanks, I followed up on https://lab.civicrm.org/dev/mail/issues/56.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2019-11-09. Score: 3 | Accepted answer
  
  I believe this is fixed with <https://github.com/civicrm/civicrm-core/pull/15780>. It will be hopefully included in a point release that should come out soon for 5.19
  
  > **Comments:**
  > **username_0**: That does solve my issue. Thanks.  
  
  ---
  
  