"If Object Exists" is still running child opeations when object DOES NOT exits

I’m checking to see if our application was left in an open state before running the entire project suite. The test app, 95% of the time, would be left open in one of three main forms: login screen, table layout, or order form.

I’ve therefore create three separate “If Object.Exists.Execute child operations if the object exists” actions, which would then take the appropriate steps to close down the application. I then created three test scenarios, where in each case, the forms DO NOT exist, however, in each case, the child operations still continue to run (therefore hanging up the test and then causing the script to fail). (Note: script does work correctly when object does exist)

I’ve correctly identified each main form object (I’ve even tried narrowing it down to several “specific” objects on each form), I’ve correctly >indented the child operations (see attached), and I’ve even broken-out the If Object statement into a separate test, which then calls the appropriate action test (see attached), but I’m still getting the same problem.

Is there something I’m missing?

PS I’m not seeing an If/Else command, which would allow the action to step out and move onto something else, so I’m presuming that as per the applied logic in the statement “ Execute child operation if the object exists”, that the converse would also be true, in that the child operations WILL NOT execute if the object does NOT EXIST.