[External] Discovery Schedules can become hung in duplicate IP processing due to duplicate device histories for same IPDescriptionYou note that when discovering servers with multiple NICs, sometimes Discovery will become hung if you are discovering independent applications (ex: Kafka) or hardware (ex: UNIX Cluster)Steps to Reproduce- Enable IP dedupe processing- Scan Server with multiple NICs- Have a pattern triggered from ADM where the CI class is independent (ex: Kafka)- Test until Kafka DH is selected for IP dedupe and note that "Skip IP" classify input is hungWorkaroundApply attached script include workaround. Validated only for Visibility Content 6.19 and 6.19.1Related Problem: PRB1786820