Broken email template references after deploying flows between environments have been a long-standing pain point. Summer '26 resolves this by storing email templates as persistent name-based references instead of record IDs.
Where
Applies to the Send Email action in any flow type that sends email using an Email Template.
How
In the Send Email action, open the Advanced options and set the Action Version to 3.0.1 or higher. Once upgraded, the template is referenced by API name rather than ID, making it portable across orgs and environments.
Why
Email template record IDs differ between sandboxes and production, causing deployed flows to lose their template reference. The name-based approach makes flows environment-agnostic for email sending.
💬 Comments
Sign in with LinkedIn to join the conversation
Loading comments...