This morning we identified an issue where users would send themselves a test email in a template and they would receive an older copy of the message. Our developers have been made aware of this and are working to resolve it quickly.
This issue won’t impact any emails that sent via broadcast or from follow-up sequence. It is isolated to only the “Save and Send Test” button found on the email editor.
There is a workaround to use in the meantime so you can test your email messages. Simply go to your own contact record and send yourself an email and choose the desired template you wish to test. Alternatively, you can also send a broadcast and target yourself as the recipient.
Sorry for the inconvenience and we appreciate your patience as we fix this. ![]()
—
UPDATE 5/13/10 2:48 PM: At this time we have identified the cause and a patch to resolve this. We anticipate to deploy the fix this evening to all applications. We apologize for the delay but thank you for your patience and understanding.
RESOLVED 5/14/10: The issue has been resolved.
{ 8 comments… read them below or add one }
Thanks for posting the issue. I thought I was going nuts!
Gary,
Thanks for letting us know. You're not going crazy; we've been able to fast-track the resolution on this so it should be fixed this evening. Thanks for your patience.
~joseph
I am having trouble when I save a change to a template in the edit screen and when I go to view it before I even test it and it won't keep the changes. I tried this several times yesterday and it wouldn't work on any of my templates
Robyn,
Thanks for commenting. The problem you describe is *exactly* the issue we're aware of. Thanks for letting us know and hope this reassures you we're on top of it and you're not going crazy.
Thanks,
Joseph
The problem is still happening.
We deployed last night with the changes, it should be working correctly – can you confirm?
Does the above problem also include not being able to send broadcasts? The workaround mentioned above says I can send a broadcast only to myself … it looks like we can't even do that. The error message is "We were temporarily unable to process your request. Please try again. "
Try logging out and in again – it broadcasts should work fine.