Journal batch is auto approved when line manager is missing in employee record

Oracle Fusion General Ledger Cloud- 23A

Recently, we have noticed a scenario in which journals are getting auto approved(over the threshold amount) when a line manager is missing/inactive in submitter's employee record. The workflow is erroring out as expected if there is only one header in the batch and if header is above threshold.

The workflow is not erroring out(it should have error out) if there are multiple headers in the batch, one header above threshold and one header below threshold. In this case batch is getting auto approved(not expected result).

Is there a way to add check in journal approval workflow to check if line manager is available and is active?