Last reviewed Sep 6, 2026
Certain requirements in the catalogue depend entirely on data from a connected system. Without that connection, Launch has no way to verify them.
What happens without the connection
Why Launch marks them N/A instead of failing them
Rather than guessing or defaulting to a fail, Launch marks these requirements N/A when the system they depend on isn't connected. This keeps the readiness score honest: it reflects what Launch can actually verify, not an assumption about what it can't see.
Getting a fuller picture
If you want a requirement like this evaluated properly, connect the relevant system. See Connecting a system: the general flow. Once connected, re-run the preflight and the requirement will resolve to a real pass or fail.