wbdutil - status message misleading after failure

See for example this - The job failed. Yet it says "Ingest complete". Propose saying "Ingest failed" instead of "Ingest complete".

C:\TEMP>wbdutil ingest data --welllog_id osdu:work-product-component--WellLog:77874e51358347b9a5a8a4309ef50bfc -p "C:\TEMP\7556_l0102_1984_comp-WDMS.las" -t %OSDUTOKEN% -c %CONFIGPATH%
Data not ingested - LAS file validation failed: Well name associated with well log record does not match well name in LAS file.
Ingest complete: Data written from 7556_l0102_1984_comp-WDMS.las to Well Log (osdu:work-product-component--WellLog:77874e51358347b9a5a8a4309ef50bfc).

Another example

C:\TEMP>wbdutil ingest data --welllog_id osdu:work-product-component--WellLog:77874e51358347b9a5a8a4309ef50bfc -p "C:\TEMP\7556_l0102_1984_comp-WDMS.las" -t %OSDUTOKEN% -c %CONFIGPATH%
Data not ingested: HTTP error: 401. Calling: 'https://r3m15.preshiptesting.osdu.aws/api/os-wellbore-ddms/ddms/v3/welllogs/osdu:work-product-component--WellLog:77874e51358347b9a5a8a4309ef50bfc'. {"reason":"Access denied","message":"The user is not authorized to perform this action. Invalid token.","status":401}

Ingest complete: Data written from 7556_l0102_1984_comp-WDMS.las to Well Log (osdu:work-product-component--WellLog:77874e51358347b9a5a8a4309ef50bfc).