Last reviewed Sep 6, 2026
Why a fix didn't clear the requirement
If a requirement fails repeatedly even after you believe you've fixed it, work through these checks.
Checks to run before escalating
- Read the requirement's own explanation carefully in the preflight report; it names exactly what condition isn't being met.
- Confirm you fixed the issue in the system the requirement actually depends on, not just in Launch itself. See Requirements that need a system connection to evaluate.
- Confirm you re-ran the preflight after making the fix; a fix doesn't update the report on its own. See Re-running a preflight after making changes.
- Check whether a field mapping issue might be involved, if the requirement seems to be reading a value that doesn't match what you actually see in the connected system.
- Check the connection's health; a stale connection may still be evaluating against old data.
If the requirement still fails after all of this, contact support with the campaign and requirement name; this may point to a field mapping issue needing correction on Launch's side.