In the Hierarchical-VPLS environment, connectivity between LDP signaled and static psuedowires will be impacted resulting in traffic drop if multiple mesh-group is configured under the same routing-instance and the name of each mesh-group is not unique i.e. substring of another mesh-group.
This issue might be seen if the following conditions are met :
* On all Junos and Junos OS Evovled platforms* H-VPLS is configured
* When user defined pseudowire mesh group name under a routing-instance is sub-string of other pseudowire for example, Pseudowire and Pseudowire_static.

Following is the command to identify the issue : 
show vpls flood instance <instance-name> extensive

Traffic between LDP signaled and static VPLS pseudowire will be blackholed.

Workaround:

User defined mesh group in VPLS(Virtual Private LAN Services) must should be unique and not substring of other mesh group names.

https://prsearch.juniper.net/problemreport/PR1772424

Resolved-In:

evo:21.2R3-S8-EVO evo:21.4R3-S7-EVO evo:22.2R3-S4-EVO evo:22.3R3-S3-EVO evo:22.4R3-S2-EVO evo:23.2R2-EVO evo:23.4R2-EVO evo:24.1R1-EVO evo:24.2R1-EVO junos:21.2R3-S8 junos:21.4R3-S7 junos:22.1R3-S6 junos:22.2R3-S4 junos:22.3R3-S3 junos:22.4R3-S2 junos:23.2R2 junos:23.4R2 junos:24.1R1 junos:24.2R1