Test is failing even if abortOnAssertionFailure is set false in external global or directly used in api command

[SDETQATestAutomation]

Test is failing even if abortOnAssertionFailure is set false in external global or directly used in api command.
As per documentation "By the default if the element is not found the test will fail. Set this to false if you wish for the test to continue even if the assertion fails. To set this globally you can define a property abortOnAssertionFailure in your globals."

   Timed out while waiting for element <//button[@id='######']> to not be visible for 30000 milliseconds. - expected "not visible" but got: "visible" (30212ms)
       at World.<anonymous> (C:\GartnerWorkspace\cpp_framework\cppworkspace\tests\stepdefs\workspace.js:89:19)
       at processTicksAndRejections (internal/process/task_queues.js:95:5)

√ After # tests\stepdefs\hooks.js:184
√ After # tests\stepdefs\hooks.js:177
√ After # node_modules\nightwatch\cucumber-js_setup_cucumber_runner.js:66

1 scenario (1 failed)
4 steps (1 failed, 3 passed)
1m12.694s (executing steps: 1m12.643s)

[swrdfish]

Tracked here: #3275