Body: <p>At this point in our application process, 'Awaiting approval' is our desired, and standard participant status. However, if a record needs altered and the status is changed away from that for the alteration, and then back to 'awaiting approval' the auto generated acknowledgement mail defaults with 'You have been added to the WAIT LIST for this event.' which isn't the case and causes concern. Is there a way to avoid this?</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-11-02T08:33:55.350Z
Comments.Text: This sounds like a bug in CiviCRM. You could uncheck the sending of e-mails as soon as you update the participant status. Not sure whether that helps you.
Comments.UserDisplayName: Jaap Jansma - CiviCooP
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-11-02T12:48:48.183Z
Comments.Text: Use a different status or an action for your administrative process. Awaiting approval does put them back on the wait list. Or change the email text.
Comments.UserDisplayName: Christia
Tags: <civievent>
Title: Changing Participant Status - generates wrong email
ThreadText: # Changing Participant Status - generates wrong email
  
  (Asked by: username_0 on 2017-11-01)
  
  At this point in our application process, 'Awaiting approval' is our desired, and standard participant status. However, if a record needs altered and the status is changed away from that for the alteration, and then back to 'awaiting approval' the auto generated acknowledgement mail defaults with 'You have been added to the WAIT LIST for this event.' which isn't the case and causes concern. Is there a way to avoid this?
  
  **Tags:** civievent
  
  > **Comments:**
  > **username_1**: This sounds like a bug in CiviCRM. You could uncheck the sending of e-mails as soon as you update the participant status. Not sure whether that helps you.  
  > **username_2**: Use a different status or an action for your administrative process. Awaiting approval does put them back on the wait list. Or change the email text.  
  
  ---
  
  ## 0 answers
  
  