Template subject line saved in Email Center does not reach the compose window
<p>Editing a template's subject in Email Center saves to the template record but does not reach compose.</p><p>Template 993617, "Customer - FBCFR 2026 VIP Passes." Removed the customer first name merge field from the subject and saved.</p><p>What happened:</p><ol><li>First save appeared to take, then reverted - reopening the template showed the old subject again.</li><li>Saved a second time. That one held. The template record shows the new subject on every reload since.</li><li>Opened a lead, Documents > Email, selected that template. mail_subject loaded the OLD subject - the one no longer in the template record.</li></ol><p>So the template and compose disagree, with compose serving the stale value. Retyped the subject by hand on all 31 sends to get the right one out.</p><p>Asking: is compose reading a cached copy of the template, and if so what clears it? We need to know a template edit is actually live before we send on it - right now the template screen showing the new subject is not evidence that it will be used.</p><p>Also worth checking why the first save silently reverted. If saves can fail without an error, that is the bigger problem of the two.</p><p>Account hbriers, Chrome 153 on macOS, 9/19/2026.</p>
The same problem
<p>Correction to the report above - I rechecked the template directly and got this wrong the first time.</p><p>Neither save persisted. Template 993617's subject field still holds its original value today: *ctfirstname*, a VIP night at the Fort Bend rodeo, on us. The edit that removed the merge field is simply not there.</p><p>So step 2 of the original report is wrong. The template record does not show the new subject. What actually happens is narrower and easier to chase: an edit to the subject field on this template does not persist, and the revert is silent - the save reports success and the field is unchanged on the next load.</p><p>That means the compose-window part of the original report may be nothing more than compose correctly serving the only subject the template has ever had. Please treat the caching theory as unconfirmed and start from the save path instead.</p><p>What we need: why a subject edit on this template reports a successful save and does not persist. If a save can fail silently on this field it can presumably fail silently on others, which is the part that worries us.</p><p>Workaround in use: retyping the subject by hand in the compose window on every send. That covered all 31 sends, so nothing wrong reached a customer.</p><p>Account hbriers, Chrome 153 on macOS.</p>
<p>Correction to the report above - I rechecked the template directly and got this wrong the first time.</p><p>Neither save persisted. Template 993617's subject field still holds its original value today: *ctfirstname*, a VIP night at the Fort Bend rodeo, on us. The edit that removed the merge field is simply not there.</p><p>So step 2 of the original report is wrong. The template record does not show the new subject. What actually happens is narrower and easier to chase: an edit to the subject field on this template does not persist, and the revert is silent - the save reports success and the field is unchanged on the next load.</p><p>That means the compose-window part of the original report may be nothing more than compose correctly serving the only subject the template has ever had. Please treat the caching theory as unconfirmed and start from the save path instead.</p><p>What we need: why a subject edit on this template reports a successful save and does not persist. If a save can fail silently on this field it can presumably fail silently on others, which is the part that worries us.</p><p>Workaround in use: retyping the subject by hand in the compose window on every send. That covered all 31 sends, so nothing wrong reached a customer.</p><p>Account hbriers, Chrome 153 on macOS.</p>
We can take a look. What is the name of the template currently? What should the subject line read?
We can take a look. What is the name of the template currently? What should the subject line read?
Thanks, Susan. This hasn’t happened since. You can close this one.
Thanks, Susan. This hasn’t happened since. You can close this one.
Thanks for advising if you have issues going forward please let us know
Thanks for advising if you have issues going forward please let us know
Replies have been locked on this page!