Lightning Email Template Error for Process Email Alert: We don't recognize field prefix Recipient - Answers - Salesforce Trailblazer Community
Trailblazer Community
Ask Search:
Emily MannEmily Mann 

Lightning Email Template Error for Process Email Alert: We don't recognize field prefix Recipient

Hi everyone,

I saw that with the release of Winter 21, you can now use Lightning Email Templates in flows and processes via email alerts.  

I have had a process setup for about a year that automatically sends a notification to the account owner when a customer (contact) is given permission to an external portal that we have, but I have always just manually sent the email to the contact using a Lightning Email Template.  Never had a problem.

When I added the email template to the email alerts  and then added the email alert to the process, though, I keep getting an email stating:

Error Message: We don't recognize the field prefix Recipient. Associate a record that matches the prefix or update the template to remove the merge field from the body, subject, or letterhead.

I've done some digging around the Trailblazer community to see if I could find a solution on this, but everything i've seen says the issue stems from not using the correct merge field language, but this does not make sense, as my template does have the {{{--}}} format that it requires, and it notes that recipient will replace contact.    I have also noticed that this only happens when I try to use the process to send the email, not if I do it manually.  

I am at a loss to figure this out, and would greatly appreciate any thoughts on what could be causing this.

Keiji OtsuboKeiji Otsubo
Hi Emily,

It is a phenomenon with VF email template, but there is no problem with manual operation, and it is the same in terms of NG in flow.

Isn't the following helpful ?

While the symptom was indeed a Visualforce Email Template, the true cause was that the running user context was the Site Guest User when firing the Workflow Rule.
It is not possible to send emails on behalf of Site Guest User. My workaround in this case was to change the Workflow Rule Email Action to a Create Task Action, which guests are permitted to own.