---
title: "Resolve preflight findings"
description: "Work through blocking findings so a version can move forward."
canonical: "https://memo.ly/docs/resolve-preflight-findings"
updated: "2026-07-31"
---

# Resolve preflight findings

Work through blocking findings so a version can move forward.

**Who this is for:** Editors fixing quality issues.

When preflight reports a blocking finding, the version cannot be approved, exported, or test sent until it’s resolved. Each finding includes evidence drawn from the compiled output.

1. **Open the preflight report** - Review findings on the draft panel or the version report.
2. **Fix the underlying issue** - Resolve unresolved variables, broken links, missing alt text, oversized markup, and similar issues in the editor.
3. **Re-run preflight** - Create a new version or re-check; passing status is recomputed for the exact content.

> For a specific unresolved variable, see [How do I resolve an unresolved variable?](https://memo.ly/help/how-do-i-resolve-an-unresolved-variable.md).

## Expected result

Blocking findings are cleared and the version can proceed.

## Common mistakes & troubleshooting

- If preflight keeps blocking export, see [Why is preflight blocking my email?](https://memo.ly/help/why-is-preflight-blocking-my-email.md).

## Related
- [Understand Email Preflight](https://memo.ly/docs/understand-email-preflight.md)
- [Understand preview datasets and variables](https://memo.ly/docs/understand-preview-datasets-and-variables.md)
- [Glossary: Quality Profile](https://memo.ly/glossary/quality-profile.md)

[View HTML version](https://memo.ly/docs/resolve-preflight-findings) · [Documentation home](https://memo.ly/docs)