Email diagnostics
Inspect structured compiler and fixture findings with source origins, repair invalid inputs, and distinguish warnings from delivery failures.
Email findings include code, severity, message and source origins. Errors stop the affected
compile or render; warnings accompany successful output. Preview and checks include fixture
findings so you can locate the source and input that produced the problem.
Needs attention lists errors and known source risks. The Compatibility report keeps client support observations separate and combines repeated findings across fixtures. Filter the report by client and assessment, then expand a finding for affected fixtures, source locations and support evidence.
| Assessment | Meaning |
|---|---|
| Risk | The emitted output uses a construct with a concrete content, navigation or rendering risk. Errors block the affected operation; warnings identify a source change to consider. |
| Needs verification | A support difference exists, but the checker has not established its effect on this template. Test the affected fixtures in the listed clients. |
| Expected difference | The client may substitute a font or show square corners. Decide whether the visual difference is acceptable. |
| Not affected | The emitted values avoid the specific limitation, such as using pixels instead of unsupported rem font sizes. This is not a claim about the whole email. |
The attention count includes errors and warnings, not every client observation. An empty attention list does not establish that the email renders correctly in every client. Outstanding client checks remain visible in the report; browser preview alone does not complete them.
When a source change is deterministic, the group offers a specific repair action. For example,
Use new-window links changes eligible literal link targets to _blank. These source edits support
Undo and Redo. Review the preview after applying a repair.
In the hosted editor, expand Fix issues with agent and choose Fix with agent for a finding group. The agent receives the findings and draft revision, inspects the project, and checks its edits against the fixtures. Review the resulting draft diff and previews before publishing. Agent edits do not use the local editor's Undo history.
Structured findings can include fixtures, occurrences and compatibility. Each occurrence
preserves its source origin chain. Compatibility findings include a consequence-based title and
an assessment of risk, unverified, degradation or not-applicable, so API and editor consumers
can distinguish source risks from observations without interpreting the message text.
- Invalid schema or fixture: repair the declared contract or fixture data.
- Duplicate id: give each definition a stable, project-unique id.
- Unsupported element, attribute or URL: use supported HTML or an email primitive.
- Missing asset base: provide the HTTPS origin serving imported delivery assets, or use local export.
- Render failure: inspect the selected fixture and the failing synchronous expression.
A failed email entry remains visible with findings and no render. Run checks after a repair and preview the affected fixtures again. Actual send inputs are validated and rendered before provider submission; successful fixture checks do not prove every branch.