Email template in Send E-Mail Smart service for an in-flight process instance

We are using an HTML template with this send email smart service. We are facing a problem while sending emails using this smart service for an in-flight process instance.
The issue is HTML template behind this email has been changed and published, but there was already a few running instances when this was published. In the new version of the template, we have new place-holder fields. The running process instance is picking up this new email template (instead of the email template version available when the process was initiated), and since this instance does not know the new placeholder fields in the newer template, it's sending emails with those placeholder values.
For example, if there is a new place-holder in this template as ###COMPANY_NAME###, the in-flight process instance sends email with ###COMPANY_NAME### in email body.
Is there a way to educate the in-flight pr...

OriginalPostID-251684