Indeed, there are some issues with the exit codes returned by the shell. When using custom exit codes, it returns code 0. The team is aware of this issue. They are currently working on it and the fix should be included in the future firmware releases.
Apologies for any inconvenience that this may have caused.
Unfortunately, we don’t have defined timelines for when this issue will be resolved. Therefore, I cannot provide a specific date for the fix, but the RnD team is actively working on it.