Guitarrista82

Thanks Darshil! I will take a look. I appreciate your help! LK

@SanfordWhiteman Regarding using a different datetime field so that I can send the email at 9 am in the person's timezone, would that be using a smart campaign or an email program?

I'm not sure the reasoning behind why the Date of Birth field was used and another field wasn't created. I imagine there was a request from another department and this was a quick solution that made sense at the time. As far as how the field is set to birth day + this year's date, it happens in two ...

Ah, good point Darshil. I do know that the email program can send emails based on recipients' timezone, but we would have to create 30 programs each month to send one Happy Birthday email, which doesn't make sense. Any potential workarounds/solutions?

Hi Sanford, To clarify, we use a field Date of Birth and set it to their birth day + this year's date.Then, in the SL it looks for people whose "Date of Birth" is Today and send them the email.

Hi Darshil, Yes, the only thing that seemed to work was to create a brand-new asset and pull the new module in...There was no way that we could use the clones of clones email assets. Everything looked good when testing the brand-new email asset. And, interestingly, the email assets that I use to tes...

Hi Christiane, Good question...It's occurring with both the draft and approved versions. Yes, from what I have read before in the Community, clones of clones of clones can become corrupted and the email will not appear/behave as expected. So definitely good practice with major changes to start from ...

Hi Darshil, Yes, I did verify using an un-cloned email asset for the master template that the errors did not appear. I will need to double check the code between the test and master templates, however. It should be the same, but there may be differences. Thank you,LK