Saga pattern: orchestration vs choreography in practice

We're dealing with distributed transactions across several microservices, and I'm looking into the Saga pattern. The main debate on our team is between orchestration and choreography. Orchestration seems simpler to understand and debug, with a central coordinator, but that coordinator could become a single point of failure. Choreography feels more resilient with services reacting to events, but tracing failures and overall flow can become incredibly complex, especially across 5+ services. In practice, when have you chosen one over the other? What are the specific scenarios or team sizes that make one approach clearly superior? Any war stories about debugging a complex choreographed saga?