This is already problematic as this particular error is reported but fails to fail the session correctly. Documented this in issue #187