Email 'to' field failing
SOLVEMy automated email workflow is pulling the email twice for contacts who put their email as their first name. How can I adjust my workflow to fix this error?
1 Accepted solution
Email 'to' field failing
SOLVEHi @RoselineKp,
@RoselineKp wrote:
My automated email workflow is pulling the email twice for contacts who put their email as their first name.
What makes you come to this conclusion? The error message states something differently: The email addresses failed validation.
Can you explain what you're referring to when you say 'pulling the email twice'?
From looking at the error message, I would say that the email addresses are simply not valid, e.g. janedoe@gmailcom, janedoe @gmail.com, janedoe@gmailco. Have you reviewed the email addresses of these four contacts?
I haven't seen this error message before and instead of referring to the Email field, it's referring to a To field. If the To field is a custom property, it would not have the regular Email field validation to check whether an email is generally valid (see the examples above). In that case, an email send would technically not be possible. Is that the case?
If you could answer my questions above, that'll bring us closer to a solution.
Best regards
| Karsten Köhler |
 | Did my post help answer your query? Help the community by marking it as a solution. |
Email 'to' field failing
SOLVEHi @RoselineKp,
@RoselineKp wrote:
My automated email workflow is pulling the email twice for contacts who put their email as their first name.
What makes you come to this conclusion? The error message states something differently: The email addresses failed validation.
Can you explain what you're referring to when you say 'pulling the email twice'?
From looking at the error message, I would say that the email addresses are simply not valid, e.g. janedoe@gmailcom, janedoe @gmail.com, janedoe@gmailco. Have you reviewed the email addresses of these four contacts?
I haven't seen this error message before and instead of referring to the Email field, it's referring to a To field. If the To field is a custom property, it would not have the regular Email field validation to check whether an email is generally valid (see the examples above). In that case, an email send would technically not be possible. Is that the case?
If you could answer my questions above, that'll bring us closer to a solution.
Best regards
| Karsten Köhler |
| Did my post help answer your query? Help the community by marking it as a solution. |
