In OIC, currently challenging to determine the parents associated with a given child integration

In Oracle Integration Cloud, it has become increasingly difficult to identify the parent integrations associated with a given child integration. For instance, if the child integration "C" is invoked by multiple parent integrations such as "A" and "B," any version change to "C" can cause parent integrations "A" and "B" to fail with errors.

[CDATA[{"details":"****_SUPP_BATC_UPDA_ORA_TO_APEX with version 01.00.0002 is not activated with the Scheduler","errorPath":"/scheduler/v1/integrations/****_SUPP_BATC_UPDA_ORA_TO_APEX%7C01.00.0002/jobs","faultName":"scheduler:APIInvocationError","httpStatusCode":400,"origin":"scheduler-78fccf7f8b-4rhds","reason":"Request payload validation error occurred while processing request: oracle.oic.scheduler.ValidationException","requestId":"I1RIALWVWPXLPUSJVECC55FYM3ZCS5BP/C3B24E92383E4FF8A697800F77A562DC/BF4A1D9668DB4897936F09AE175E9337","retriable":false,"traceId":"cf21bd9eceb0b67b"}.A 400 Bad Request Error indicates that the target service is unable (or refuses) to process the request sent by the client (Oracle Integration Cloud), due to an issue that is perceived by the server to be a client problem. Try invoking the target service using cURL. It may also be that one of the intermediaries (proxy, LBR) could be returning this code. ]]></ns2:instance></ns2:errorDetails></ns2:APIInvocationError> ]