When is a distributed transaction, with all its extra hassle, actually worth doing?

Hey everyone, I've been struggling lately with operations that spread across a bunch of different services and databases. Making sure everything is atomic is turning into a real pain. I'm trying to figure out when it's actually worth using a distributed transaction strategy, like the Two-Phase Commit or the Saga pattern. For simpler stuff, I've found that just fixing things manually or using eventual consistency with retries works fine. But as more services get involved, the risk of things getting out of sync just keeps going up. So, what makes you decide to bring in something like a Saga into your system? Are there certain business needs, like really strict financial accuracy or super complicated workflows, that immediately make you think of these more complex solutions? Or do you try to put them off for as long as you can because of all the extra work involved?