Native Scheduler does not properly track Core exit code
Detected in build:
Published in build:
For instance, Core exits with "1" but Native Scheduler says that its exit code is "0" (perhaps always).
This is one more crucial issue related with recent fixes and improvements in schedulers.