Handling Cross-Service Transactions in Microservices: Sagas vs. Two-Phase Commit (2PC)?

Hey everyone, I'm working on a new service that needs to orchestrate actions across several existing microservices. Specifically, there's a user action that triggers updates in an inventory service, a payment service, and a notification service. If any of these sub-operations fail, we need to roll back or compensate for the others to maintain data consistency. I've been looking into Sagas as the primary approach, but I'm also wondering if there are specific scenarios where a more traditional 2PC might still be considered, despite its well-known drawbacks in distributed systems. Has anyone implemented complex transactional workflows like this? What were your experiences with Sagas, especially concerning error handling and compensation logic? Are there any hidden gotchas or better patterns for ensuring data integrity across service boundaries without introducing a centralized transaction coordinator for everything?