Service Mapping discovery tries specific patterns with entry point type TCP Endpoint. From agentlog, it shows: PatternFilter{producedCIT='cmdb_ci_...',Issue When creating a new map with TCP Endpoint as entry point, in most cases, Service Mapping runs through all Application patterns and completes the one that matches. If no Application pattern matches, it runs Generic Application pattern. However, if the Endpoint is actually already created in another Service Map (for example, as a connection created by a pattern), and has target CI Type associated, it will only try patterns that matches that CI Type. And you may see below in MID server agent log during debugging: PatternFilter{producedCIT='cmdb_ci_...',ResolutionThis is working as expected. To confirm CI Type, review sa_ci_attr table. To find current Service Map that uses the endpoint, on svc_ci_assoc table, search for the endpoint under Configuration Item Id field. Open the Map, locate the connection, and check discovery pattern log from parent node, review create connection step.