Process status in error scenarios

Hi,

Currently we have number of processes where a bpmn error is thrown in child processes and not handled by parent process, this could have happened unintentionally and in such cases child abruptly ends process and there is no track of if the child process was errored out.
One example : an HTTP connector task where response cannot be parsed

I do understand we could overwrite this behavior with flag enableExceptionsAfterUnhandledBpmnError which is mentioned here Error Events | docs.camunda.org
However I dont want my process to go in error state and at the same time I want to know if my child was completed successfully or had a bpmn error in between that I did not catch especially where we are integrating multiple API endpoints in orchestration.

Is there a way to capture process status like InProgress, completed, failed, terminated etc, I understand history captures some of it not sure if it covers the scenario above