when would you say the saga pattern is too much for microservices, really. like, when is it just not worth the hassle

hey everyone, ive been working w/ microservices that need to maintain data consistency across several independent services. weve implemented the saga pattern in a few places, and its definitely helped avoid distributed transactions. but, for some simpler workflows, it feels like were adding a lot of complexity just to manage compensating transactions and state. what are your thoughts? when have you found the saga pattern to be the right tool for the job, and when have you opted for simpler alternatives or refactored to reduce the need for it