Previewing and Testing Email Templates

Two checks are available before a template goes live: Preview renders it against a real record without sending anything, and Send Test Email delivers a marked copy to a small recipient list without triggering the automation that normally sends it.

Both require only Read permission on the Email Template object. Note that this means a user who can only view templates can still send a real test email.

Previewing Against a Record

In the editor, choose Actions > Preview.
On Preview the template with the following record, choose an entity, search for a record, select it, and click Next.
The preview opens full-page, showing the rendered email as it would arrive.
Click Back to edit to return.

From the preview you can:

switch between Desktop, Tablet and Mobile;
switch which portal's branding is applied using the Branding dropdown, which offers Main Portal plus each hub;
click Copy HTML to copy the rendered markup;
click the record pill to change the record.

Unresolved tokens are listed. If any merge token could not be resolved against the chosen record, a warning reports N merge token(s) couldn’t be resolved against this record: and names them, so you can correct the token or pick a different record. This is the only place these surface - at send time they are silently removed.

Sending a Test Email

Choose Actions > Send Test Email in the editor, or Send Test Email from the row's action menu on the list page.
Enter recipients in Send test to, pressing Enter after each. Your own address is pre-filled.
Choose the record whose values the merge tokens should render against.
Review the recipients and record, then click Send test.

Behavior	Detail
Recipient limit	5 per send. Fixed and not configurable.
Subject	Prefixed with [TEST].
Automations	Downstream workflows do not fire. Sending a test does not trigger the automation that normally sends the template.
Language	Each recipient receives the message in their own resolved language, so a test is a genuine check of your translations.
Email quota	Tests count toward your organization's daily email limit.

About the daily email limit. Your organization has a rolling 24-hour email quota. Once it is reached, no further email is sent until the window rolls over, and administrators are notified by email both as the quota is approached and when it is exceeded. Raising the quota is a request to Magentrix, not a self-service setting - contact your Magentrix representative. Keep this in mind before running a large batch of tests.

Choosing a Record

Both the preview and the test-send record pickers behave the same way:

Only entities that support automation are listed.
Before you search, the ten most recently modified records are shown; searching widens the result set.
Record visibility follows your normal access to those records.

Choose a record that actually populates the fields your tokens reference. A record with empty values will make tokens look broken when they are merely blank.

What Preview Does Not Cover

Attachments are not included. Files attached to the email are added by the automation that sends it, not by the template.
The real send pipeline is not exercised. Preview is a content check, not a delivery test. Use a test send to confirm delivery, rendering in a real mail client, and language resolution.

Messages You May See

Message	Cause
That doesn’t look like a valid email address.	A test-send recipient is not a valid address.
Up to 5 recipients per send test (received N).	More than five test recipients were supplied.
Provide at least one recipient.	A test send was submitted with no recipients.
Pick a record to merge against.	A preview or test send was submitted without a record.
N merge token(s) couldn’t be resolved against this record:	The preview record has no value for those tokens, or the token names do not match the entity's fields.

<< Localizing Email Templates | Email Templates Reference >>