Pattern name: Google Cloud Platform (GCP) – Load Balancer – TCP – UDP - not creating LB Pool due to IRE Missing Dependency ErrorDescriptionThe Google Cloud Platform (GCP) – Load Balancer – TCP – UDP pattern fails to create an LB Pool due to an error indicating missing dependencies for the `cmdb_ci_lb_pool` class. This occurs when the payload processing step detects no valid relations defined for `cmdb_ci_lb_pool` that match containment/hosting rules, such as allocation to `cmdb_ci_lb_service` or hosting on `cmdb_ci_cloud_load_balancer`. The issue arises in environments where Network Endpoint Groups are configured in GCP, as the pattern previously parsed only instanceGroups and required updates to handle networkEndpointGroups. Steps to Reproduce The issue is reproduce only if you have configured Network Endpoint Goups in GCP, doc reference below:https://docs.cloud.google.com/load-balancing/docs/negs 1. Configure Network Endpoint Groups in a GCP environment. 2. Run the GCP Cloud Resource Discovery process. 3. After discovery completes, check the pattern logs for the Google Cloud Platform (GCP) – Load Balancer – TCP – UDP pattern. 4. Navigate to the "Payload processing" section and review "Check For Output Payload Errors." 5. Observe the error: "In payload no relations defined for dependent class [cmdb_ci_lb_pool] that matches any containment/hosting rules."Workaround1. Please download attached pattern XML file and do an "Import XML file" to the affected instance. 2. Verify that the pattern record for "Google Cloud Platform (GCP) - Get TCP - UDP Cloud Pool Manually" is updated. 3. To confirm that the pattern is updated on the MIDs please check ECC Queue with Name "sa_pattern" and Source "FileChange" were created around the time when you have done the import. There should be a pair of input and output ECC Queue records for each MID server with status "Up". Alternatively, the same process can be done manually in form view of the pattern "Google Cloud Platform (GCP) - Get TCP - UDP Cloud Pool Manually -> Related links> click on Synchronize with MID ServersRelated Problem: PRB1982309