How to handle nested roll back issues when SAGA pattern is used for transactional handling cutting across multple microservices

Question

when transaction goes across more than 1 microservices each having its own isolated db persistence, how to handle roll back failure ..Say we have 3 microservices, MS1, MS2,