Answers.Body: <p>We had this bug in specific versions of CiviCRM. My advice is to upgrade to later versions, its very difficult to track down the exact cause. A few JIRA tickets exist around it, you can search but my advice would still be to upgrade to a newer version.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-03-24T15:42:21.440Z
Answers.LastActivityDate: 2017-03-24T15:42:21.440Z
Answers.UserDisplayName: Parvez Saleh
Answers.Body: <p>Check under-the-hood. If the "execute query" was double clicked, could that have caused this?</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-03-20T05:19:11.103Z
Answers.LastActivityDate: 2017-03-20T05:19:11.103Z
Answers.UserDisplayName: JohnFF
Answers.Body: <p>Have encountered the 200% delivery rate on a few mailings in Civi 4.6.33 . Found that there was a duplicate set of mailing jobs (parent + children), which were sent a couple of hours after the first set.</p>
  
  <p>In this case, it appears the issue may be down to mailing approval workflow: log_civicrm_mailing indicates that somehow the affected mailings had their approval date changed, suggesting they were re-approved a while after the initial send had completed. The second send then began after this second approval.</p>
  
  <p>This occurred during periods of heavy database load, so it's possibly a user clicked Approve multiple times after not getting an initial response, though that wouldn't explain the delay. In at least one case, the user who created the mailing had permission to approve, so may have hit Approve &amp; Send more than once.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-02-08T16:15:26.680Z
Answers.LastActivityDate: 2018-02-08T16:15:26.680Z
Answers.UserDisplayName: davejenx
Body: <p>It is CiviCRM 4.6.14. The mailing was scheduled via the api as per <a href="https://civicrm.stackexchange.com/questions/17625/how-do-i-get-civicrm-mailing-to-submit-via-the-api%20stackexchange%20question">this stackexchange question</a>.</p>
  
  <p>It appears to have sent all the messages twice. Any ideas why? See report. </p>
  
  <p><a href="https://i.sstatic.net/DNuIf.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/DNuIf.png" alt="enter image description here"></a></p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-03-20T05:18:33.467Z
Comments.Text: Please could you tell us what extensions you have installed?
Comments.UserDisplayName: JohnFF
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-03-20T05:21:15.553Z
Comments.Text: I've only got custom extensions installed. 3 things that add activities to members when they get sent journals.
Comments.UserDisplayName: Interlated
Tags: <civimail><api>
Title: CiviCRM mail sent 200% of intended recipients. Why?
ThreadText: # CiviCRM mail sent 200% of intended recipients. Why?
  
  (Asked by: username_0 on 2017-03-20)
  
  It is CiviCRM 4.6.14. The mailing was scheduled via the api as per [this stackexchange question](https://civicrm.stackexchange.com/questions/17625/how-do-i-get-civicrm-mailing-to-submit-via-the-api%20stackexchange%20question).
  
  It appears to have sent all the messages twice. Any ideas why? See report.
  
  [![enter image description here](https://i.sstatic.net/DNuIf.png)](https://i.sstatic.net/DNuIf.png)
  
  **Tags:** civimail, api
  
  > **Comments:**
  > **username_1**: Please could you tell us what extensions you have installed?  
  > **username_0**: I've only got custom extensions installed. 3 things that add activities to members when they get sent journals.  
  
  ---
  
  ## 3 answers
  
  ### Answer by username_2 on 2017-03-24. Score: 1 | Accepted answer
  
  We had this bug in specific versions of CiviCRM. My advice is to upgrade to later versions, its very difficult to track down the exact cause. A few JIRA tickets exist around it, you can search but my advice would still be to upgrade to a newer version.
  
  
  ---
  
  ### Answer by username_1 on 2017-03-20. Score: 1
  
  Check under-the-hood. If the "execute query" was double clicked, could that have caused this?
  
  
  ---
  
  ### Answer by username_3 on 2018-02-08. Score: 0
  
  Have encountered the 200% delivery rate on a few mailings in Civi 4.6.33 . Found that there was a duplicate set of mailing jobs (parent + children), which were sent a couple of hours after the first set.
  
  In this case, it appears the issue may be down to mailing approval workflow: log\_civicrm\_mailing indicates that somehow the affected mailings had their approval date changed, suggesting they were re-approved a while after the initial send had completed. The second send then began after this second approval.
  
  This occurred during periods of heavy database load, so it's possibly a user clicked Approve multiple times after not getting an initial response, though that wouldn't explain the delay. In at least one case, the user who created the mailing had permission to approve, so may have hit Approve & Send more than once.
  
  
  ---
  
  