It seems the NAL apps work this way, but not sure if it's supposed to.

APP1 is set for forced run, wait on forced run, priority 2 (MSI-based
app with one .MSP file)

APP2 is set for forced run, wait on forced run, priority 3 (msiexec.exe
app)

App2 is set to only run if the first app isn't installed (based upon a
registry key string value)

What seems to happen is this:

NAL Explorer runs.

It distributes APP1 and the .MSP
It then tries to run APP2 even though the registry key is there.

If I set APP2 to a "manual" run and always show icon, I can see that it
"thinks" the requirements have been met.

BUT, if I do this on a clean machine (again), and exit the NAL and
restart the NAL (explorer mind you), then APP2 shows that it should NOT
run.

It seems that at the time NAL runs (even if it hasn't gotten to the app
distribution yet), it has already evaluated all the system requirements
of the apps, instead of waiting until APP1 is done, then trying to run
APP2 and reading the registry.

Is this normal?