when do you need a saga pattern

I've been seeing the Saga pattern pop up more often when talking about distributed transactions, especially in microservice architectures. It seems like a way to manage data consistency across multiple services without using traditional two-phase commit, which can be a blocking pain. What are your experiences with Sagas? When did you find it necessary to implement this pattern versus other consistency models? Are there specific scenarios where it really shines or becomes overly complex?