That isn't true, laziness will punch straight through a tight definition of error code handling.

After all if you have three API layers realizing in this situation the second layer isn't forwarding that error code because it erroneously thought it was one you hide behind a generic one is pretty common.