Email action or document email did not go out: no valid recipient, or the message is incomplete

Question 1

Why do I see "no_recipients: No valid email address after rendering the recipients"?

Accepted Answer

- The To line must end up as real addresses. A Send email action's To holds up to 20
  entries, each either an address (sales@yourfirm.in) or a merge field such as {{ contact.email }}
  that is filled in from the record when the rule runs. The entries are split at commas, semicolons
  and spaces, and only text that looks like an email address is kept. When the buyer, member or payer
  on the record has no email address, or a merge field names something that doesn't exist (it then
  comes out blank), nothing is left to send to, and the run stops rather than drop the email
  silently. The seeded customer rules send to {{ contact.email }}, the email of the record's contact.
- Every email needs a subject and a body. A Send email action takes both from a message
  template, or from its own Subject and Body. Without either there is nothing to send, so the
  rule isn't saved. For the same reason an Email message template must have a subject.
- A void document is withdrawn. Voiding marks a document as sent in error or wrong; it stays on
  file with its number, but it is never sent again. The Email icon is hidden on void documents, so
  you only meet this when the document was voided while your page was open.

Generate document actions behave differently: their Email to (optional) is also filled in
from the record, but when no valid address comes out the document is still generated and filed on
the record, the email is simply skipped, and the run ends Success. If a letter was generate 1. Give the contact an email address. Open the run's Record link, find the buyer, member or
   payer, and add their email on Contacts (the Edit
   permission on Contacts; in the default roles the Administrator, the Sales Manager, the
   Sales Executive, the Project Manager, the Accountant, the Rehab Officer and Front
   Desk). Then press Retry in the run panel on
   Runs (the Edit permission on Workflow Runs;
   the Administrator in the default roles). The rule must still be active.
2. Correct the To line. If the address is wrong for every record, open the
   Rule, check each entry in To (use the Template
   variables reference on the action for merge field names), and click Save changes (the
   Edit permission on Workflow Rules). A system rule can't be edited: Clone it, change the
   copy, switch the copy on and the original off.
3. Skip records without an email. To stop runs failing for contacts who have no email, add a
   condition in the action's Only when… block: pick contact.… under Related rows and
   complete it as contact.email, choose the operator != and type null as the value. The step is then
   skipped for those records and the run continues.
4. Complete the email in the rule. In the Send email action, either pick an Email
   template under Use a message template, or choose Write the email here and fill both
   Subject and Body. Then Create rule or Save changes.
5. Complete the message template. Type a Subject (merge fields work there too) and click
   Create tem

Question 2

Why do I see "SEND_EMAIL failed: no_recipients: No valid email address after rendering the recipients"?

Accepted Answer

- The To line must end up as real addresses. A Send email action's To holds up to 20
  entries, each either an address (sales@yourfirm.in) or a merge field such as {{ contact.email }}
  that is filled in from the record when the rule runs. The entries are split at commas, semicolons
  and spaces, and only text that looks like an email address is kept. When the buyer, member or payer
  on the record has no email address, or a merge field names something that doesn't exist (it then
  comes out blank), nothing is left to send to, and the run stops rather than drop the email
  silently. The seeded customer rules send to {{ contact.email }}, the email of the record's contact.
- Every email needs a subject and a body. A Send email action takes both from a message
  template, or from its own Subject and Body. Without either there is nothing to send, so the
  rule isn't saved. For the same reason an Email message template must have a subject.
- A void document is withdrawn. Voiding marks a document as sent in error or wrong; it stays on
  file with its number, but it is never sent again. The Email icon is hidden on void documents, so
  you only meet this when the document was voided while your page was open.

Generate document actions behave differently: their Email to (optional) is also filled in
from the record, but when no valid address comes out the document is still generated and filed on
the record, the email is simply skipped, and the run ends Success. If a letter was generate 1. Give the contact an email address. Open the run's Record link, find the buyer, member or
   payer, and add their email on Contacts (the Edit
   permission on Contacts; in the default roles the Administrator, the Sales Manager, the
   Sales Executive, the Project Manager, the Accountant, the Rehab Officer and Front
   Desk). Then press Retry in the run panel on
   Runs (the Edit permission on Workflow Runs;
   the Administrator in the default roles). The rule must still be active.
2. Correct the To line. If the address is wrong for every record, open the
   Rule, check each entry in To (use the Template
   variables reference on the action for merge field names), and click Save changes (the
   Edit permission on Workflow Rules). A system rule can't be edited: Clone it, change the
   copy, switch the copy on and the original off.
3. Skip records without an email. To stop runs failing for contacts who have no email, add a
   condition in the action's Only when… block: pick contact.… under Related rows and
   complete it as contact.email, choose the operator != and type null as the value. The step is then
   skipped for those records and the run continues.
4. Complete the email in the rule. In the Send email action, either pick an Email
   template under Use a message template, or choose Write the email here and fill both
   Subject and Body. Then Create rule or Save changes.
5. Complete the message template. Type a Subject (merge fields work there too) and click
   Create tem

Question 3

Why do I see "SEND_EMAIL needs a message_template_id or both subject and body"?

Accepted Answer

- The To line must end up as real addresses. A Send email action's To holds up to 20
  entries, each either an address (sales@yourfirm.in) or a merge field such as {{ contact.email }}
  that is filled in from the record when the rule runs. The entries are split at commas, semicolons
  and spaces, and only text that looks like an email address is kept. When the buyer, member or payer
  on the record has no email address, or a merge field names something that doesn't exist (it then
  comes out blank), nothing is left to send to, and the run stops rather than drop the email
  silently. The seeded customer rules send to {{ contact.email }}, the email of the record's contact.
- Every email needs a subject and a body. A Send email action takes both from a message
  template, or from its own Subject and Body. Without either there is nothing to send, so the
  rule isn't saved. For the same reason an Email message template must have a subject.
- A void document is withdrawn. Voiding marks a document as sent in error or wrong; it stays on
  file with its number, but it is never sent again. The Email icon is hidden on void documents, so
  you only meet this when the document was voided while your page was open.

Generate document actions behave differently: their Email to (optional) is also filled in
from the record, but when no valid address comes out the document is still generated and filed on
the record, the email is simply skipped, and the run ends Success. If a letter was generate 1. Give the contact an email address. Open the run's Record link, find the buyer, member or
   payer, and add their email on Contacts (the Edit
   permission on Contacts; in the default roles the Administrator, the Sales Manager, the
   Sales Executive, the Project Manager, the Accountant, the Rehab Officer and Front
   Desk). Then press Retry in the run panel on
   Runs (the Edit permission on Workflow Runs;
   the Administrator in the default roles). The rule must still be active.
2. Correct the To line. If the address is wrong for every record, open the
   Rule, check each entry in To (use the Template
   variables reference on the action for merge field names), and click Save changes (the
   Edit permission on Workflow Rules). A system rule can't be edited: Clone it, change the
   copy, switch the copy on and the original off.
3. Skip records without an email. To stop runs failing for contacts who have no email, add a
   condition in the action's Only when… block: pick contact.… under Related rows and
   complete it as contact.email, choose the operator != and type null as the value. The step is then
   skipped for those records and the run continues.
4. Complete the email in the rule. In the Send email action, either pick an Email
   template under Use a message template, or choose Write the email here and fill both
   Subject and Body. Then Create rule or Save changes.
5. Complete the message template. Type a Subject (merge fields work there too) and click
   Create tem

Question 4

Why do I see "Add at least one valid email address"?

Accepted Answer

- The To line must end up as real addresses. A Send email action's To holds up to 20
  entries, each either an address (sales@yourfirm.in) or a merge field such as {{ contact.email }}
  that is filled in from the record when the rule runs. The entries are split at commas, semicolons
  and spaces, and only text that looks like an email address is kept. When the buyer, member or payer
  on the record has no email address, or a merge field names something that doesn't exist (it then
  comes out blank), nothing is left to send to, and the run stops rather than drop the email
  silently. The seeded customer rules send to {{ contact.email }}, the email of the record's contact.
- Every email needs a subject and a body. A Send email action takes both from a message
  template, or from its own Subject and Body. Without either there is nothing to send, so the
  rule isn't saved. For the same reason an Email message template must have a subject.
- A void document is withdrawn. Voiding marks a document as sent in error or wrong; it stays on
  file with its number, but it is never sent again. The Email icon is hidden on void documents, so
  you only meet this when the document was voided while your page was open.

Generate document actions behave differently: their Email to (optional) is also filled in
from the record, but when no valid address comes out the document is still generated and filed on
the record, the email is simply skipped, and the run ends Success. If a letter was generate 1. Give the contact an email address. Open the run's Record link, find the buyer, member or
   payer, and add their email on Contacts (the Edit
   permission on Contacts; in the default roles the Administrator, the Sales Manager, the
   Sales Executive, the Project Manager, the Accountant, the Rehab Officer and Front
   Desk). Then press Retry in the run panel on
   Runs (the Edit permission on Workflow Runs;
   the Administrator in the default roles). The rule must still be active.
2. Correct the To line. If the address is wrong for every record, open the
   Rule, check each entry in To (use the Template
   variables reference on the action for merge field names), and click Save changes (the
   Edit permission on Workflow Rules). A system rule can't be edited: Clone it, change the
   copy, switch the copy on and the original off.
3. Skip records without an email. To stop runs failing for contacts who have no email, add a
   condition in the action's Only when… block: pick contact.… under Related rows and
   complete it as contact.email, choose the operator != and type null as the value. The step is then
   skipped for those records and the run continues.
4. Complete the email in the rule. In the Send email action, either pick an Email
   template under Use a message template, or choose Write the email here and fill both
   Subject and Body. Then Create rule or Save changes.
5. Complete the message template. Type a Subject (merge fields work there too) and click
   Create tem

Question 5

Why do I see "A void document cannot be sent"?

Accepted Answer

- The To line must end up as real addresses. A Send email action's To holds up to 20
  entries, each either an address (sales@yourfirm.in) or a merge field such as {{ contact.email }}
  that is filled in from the record when the rule runs. The entries are split at commas, semicolons
  and spaces, and only text that looks like an email address is kept. When the buyer, member or payer
  on the record has no email address, or a merge field names something that doesn't exist (it then
  comes out blank), nothing is left to send to, and the run stops rather than drop the email
  silently. The seeded customer rules send to {{ contact.email }}, the email of the record's contact.
- Every email needs a subject and a body. A Send email action takes both from a message
  template, or from its own Subject and Body. Without either there is nothing to send, so the
  rule isn't saved. For the same reason an Email message template must have a subject.
- A void document is withdrawn. Voiding marks a document as sent in error or wrong; it stays on
  file with its number, but it is never sent again. The Email icon is hidden on void documents, so
  you only meet this when the document was voided while your page was open.

Generate document actions behave differently: their Email to (optional) is also filled in
from the record, but when no valid address comes out the document is still generated and filed on
the record, the email is simply skipped, and the run ends Success. If a letter was generate 1. Give the contact an email address. Open the run's Record link, find the buyer, member or
   payer, and add their email on Contacts (the Edit
   permission on Contacts; in the default roles the Administrator, the Sales Manager, the
   Sales Executive, the Project Manager, the Accountant, the Rehab Officer and Front
   Desk). Then press Retry in the run panel on
   Runs (the Edit permission on Workflow Runs;
   the Administrator in the default roles). The rule must still be active.
2. Correct the To line. If the address is wrong for every record, open the
   Rule, check each entry in To (use the Template
   variables reference on the action for merge field names), and click Save changes (the
   Edit permission on Workflow Rules). A system rule can't be edited: Clone it, change the
   copy, switch the copy on and the original off.
3. Skip records without an email. To stop runs failing for contacts who have no email, add a
   condition in the action's Only when… block: pick contact.… under Related rows and
   complete it as contact.email, choose the operator != and type null as the value. The step is then
   skipped for those records and the run continues.
4. Complete the email in the rule. In the Send email action, either pick an Email
   template under Use a message template, or choose Write the email here and fill both
   Subject and Body. Then Create rule or Save changes.
5. Complete the message template. Type a Subject (merge fields work there too) and click
   Create tem

Question 6

Why do I see "Email templates need a subject"?

Accepted Answer

- The To line must end up as real addresses. A Send email action's To holds up to 20
  entries, each either an address (sales@yourfirm.in) or a merge field such as {{ contact.email }}
  that is filled in from the record when the rule runs. The entries are split at commas, semicolons
  and spaces, and only text that looks like an email address is kept. When the buyer, member or payer
  on the record has no email address, or a merge field names something that doesn't exist (it then
  comes out blank), nothing is left to send to, and the run stops rather than drop the email
  silently. The seeded customer rules send to {{ contact.email }}, the email of the record's contact.
- Every email needs a subject and a body. A Send email action takes both from a message
  template, or from its own Subject and Body. Without either there is nothing to send, so the
  rule isn't saved. For the same reason an Email message template must have a subject.
- A void document is withdrawn. Voiding marks a document as sent in error or wrong; it stays on
  file with its number, but it is never sent again. The Email icon is hidden on void documents, so
  you only meet this when the document was voided while your page was open.

Generate document actions behave differently: their Email to (optional) is also filled in
from the record, but when no valid address comes out the document is still generated and filed on
the record, the email is simply skipped, and the run ends Success. If a letter was generate 1. Give the contact an email address. Open the run's Record link, find the buyer, member or
   payer, and add their email on Contacts (the Edit
   permission on Contacts; in the default roles the Administrator, the Sales Manager, the
   Sales Executive, the Project Manager, the Accountant, the Rehab Officer and Front
   Desk). Then press Retry in the run panel on
   Runs (the Edit permission on Workflow Runs;
   the Administrator in the default roles). The rule must still be active.
2. Correct the To line. If the address is wrong for every record, open the
   Rule, check each entry in To (use the Template
   variables reference on the action for merge field names), and click Save changes (the
   Edit permission on Workflow Rules). A system rule can't be edited: Clone it, change the
   copy, switch the copy on and the original off.
3. Skip records without an email. To stop runs failing for contacts who have no email, add a
   condition in the action's Only when… block: pick contact.… under Related rows and
   complete it as contact.email, choose the operator != and type null as the value. The step is then
   skipped for those records and the run continues.
4. Complete the email in the rule. In the Send email action, either pick an Email
   template under Use a message template, or choose Write the email here and fill both
   Subject and Body. Then Create rule or Save changes.
5. Complete the message template. Type a Subject (merge fields work there too) and click
   Create tem

Question 7

Why do I see "Email templates need a subject."?

Accepted Answer

- The To line must end up as real addresses. A Send email action's To holds up to 20
  entries, each either an address (sales@yourfirm.in) or a merge field such as {{ contact.email }}
  that is filled in from the record when the rule runs. The entries are split at commas, semicolons
  and spaces, and only text that looks like an email address is kept. When the buyer, member or payer
  on the record has no email address, or a merge field names something that doesn't exist (it then
  comes out blank), nothing is left to send to, and the run stops rather than drop the email
  silently. The seeded customer rules send to {{ contact.email }}, the email of the record's contact.
- Every email needs a subject and a body. A Send email action takes both from a message
  template, or from its own Subject and Body. Without either there is nothing to send, so the
  rule isn't saved. For the same reason an Email message template must have a subject.
- A void document is withdrawn. Voiding marks a document as sent in error or wrong; it stays on
  file with its number, but it is never sent again. The Email icon is hidden on void documents, so
  you only meet this when the document was voided while your page was open.

Generate document actions behave differently: their Email to (optional) is also filled in
from the record, but when no valid address comes out the document is still generated and filed on
the record, the email is simply skipped, and the run ends Success. If a letter was generate 1. Give the contact an email address. Open the run's Record link, find the buyer, member or
   payer, and add their email on Contacts (the Edit
   permission on Contacts; in the default roles the Administrator, the Sales Manager, the
   Sales Executive, the Project Manager, the Accountant, the Rehab Officer and Front
   Desk). Then press Retry in the run panel on
   Runs (the Edit permission on Workflow Runs;
   the Administrator in the default roles). The rule must still be active.
2. Correct the To line. If the address is wrong for every record, open the
   Rule, check each entry in To (use the Template
   variables reference on the action for merge field names), and click Save changes (the
   Edit permission on Workflow Rules). A system rule can't be edited: Clone it, change the
   copy, switch the copy on and the original off.
3. Skip records without an email. To stop runs failing for contacts who have no email, add a
   condition in the action's Only when… block: pick contact.… under Related rows and
   complete it as contact.email, choose the operator != and type null as the value. The step is then
   skipped for those records and the run continues.
4. Complete the email in the rule. In the Send email action, either pick an Email
   template under Use a message template, or choose Write the email here and fill both
   Subject and Body. Then Create rule or Save changes.
5. Complete the message template. Type a Subject (merge fields work there too) and click
   Create tem

Email action or document email did not go out: no valid recipient, or the message is incomplete

Messages this explains

Email action or document email did not go out: no valid recipient, or the message is incomplete

What you see

Why it happens

How to fix it

Related