Dependent relationship missing: CI relationship not created

The target CI for the relationship was not found in the cmdb_ci table or has been filtered out by Discovery patterns, causing the relationship creation to fail. (high likelihood)

The relationship type discovered does not match any existing entries in the cmdb_rel_type table, or the relationship type is inactive. (high likelihood)

The CI class of one or both endpoints does not support the discovered relationship type based on the relationship type configuration. (medium likelihood)

Discovery patterns or transform maps are incorrectly configured, preventing proper CI identification or relationship mapping during the discovery process. (medium likelihood)

ACL restrictions or insufficient permissions prevent the Discovery user from creating relationships in the cmdb_rel_ci table. (low likelihood)

Step 1: Navigate to Discovery > Status and locate the failed discovery to review the detailed error logs and identify the specific CIs and relationship type involved.

Step 2: Check if both source and target CIs exist in Configuration > Servers > CI Class Manager or directly in the cmdb_ci table using the serial numbers or identifiers from the error.

Step 3: Verify the relationship type exists and is active by navigating to Configuration > Relationships > CI Relationship Types and searching for the relationship mentioned in the discovery logs.

Step 4: Review the relationship type configuration to ensure both CI classes are supported as valid parent and child types for the discovered relationship.

Step 5: Examine Discovery patterns under Discovery > Classification/Identification to verify they correctly identify and classify the CIs involved in the failed relationship.

Step 6: Check the transform maps in System Import Sets > Transform Maps for any custom logic that might be filtering out CIs or relationships during the discovery process.

Step 7: Verify the Discovery service account has appropriate roles including discovery_admin and sufficient ACL permissions to create records in cmdb_rel_ci table.

Step 8: Re-run the discovery on the affected device range and monitor the ECC queue under Discovery > ECC Queue to confirm relationship creation succeeds.