Well there are many reasons, but let me write a few of them.
1. You do not have a NAT 0 statement in the remote ASA.
2. You have a different route in the remote ASA for the "LOCAL ASA" network.
- Or also a route beyond the remote ASA not sending the traffic back properly.
3. There is security rule in the ASA dropping the packets
- Like a FW rule or something.
- Or an ACL in the inside or even the outside (maybe sysopt connection permit vpn is off and you need to explicitly let the traffic in the ACL )
4. Maybe another tunnel with the same source and destination. (also look for incomplete configurations)
5. Maybe you are hitting the BUG related to the ASA stopping to encrypt (a reload should alleviate the issue)
Of course to detect if you are matching any of this possible scenarios a troubleshooting is necessary.
You can use the packet tracer command and also a capture for the type asp-drop, sourced ping, debug icmp trace, etc...