Customer configured EVPN-VXLAN and EVPN-MPLS Stitching, but started to observer RPD coredumping.

snip of the configure as below:

user@mx304> show configuration routing-instances Interconnect_Instance_VLAN_102-104 
instance-type virtual-switch;
protocols {
    evpn {
        encapsulation vxlan;
        extended-vni-list [ 102 103 104 ];
        interconnect {
            vrf-target target:65000:102;
            route-distinguisher 1.1.1.1:102;
            esi {
                00:12:22:32:42:52:62:72:82:92;
                all-active;
            }
            interconnected-vlan-list [ 102 103 104 ];
            encapsulation mpls;
        }
        vni-options {
            vni 102 {
                vrf-target target:1:102;
            }
            vni 103 {
                vrf-target target:1:103;
            }
            vni 104 {
                vrf-target target:1:104;
            }
        }
    }
}

Customer configured EVPN-VXLAN and EVPN-MPLS Stitching, but started to observer RPD coredumping.

Per Juniper document, https://www.juniper.net/documentation/us/en/software/junos/cli-reference/topics/ref/statement/interconnect-edit-routing-instances-protocols-evpn.html,

whenever the 'routing-instances <> protocols evpn interconnect' is configured, the 'protocols evpn interconnect-multihoming-peer-gateway' is needed at global level.

(Required for iGW devices with interconnect gateway multihoming) A list of the iGW device's peer multihoming iGW devices.

On each iGW device, configure the interconnect-multihoming-peer-gateways statement at the global [edit protocols evpn] hierarchy level to specify the IP loopback addresses of that device's peer multihoming iGW devices. This option simplifies control plane route handling to optimize forwarding among the peer iGW devices, and helps avoid loops during EVPN configuration changes. 

With JUNOS-EVO release 22.2R2 and onwards, a commit check has been added. But it is missing in JUNOS release, customers need check if the configure is complete by themseleves.