Our team (not at liberty to say which company unfortunately) moved away from Clojure back to Scala, or more accurately we built a couple of production services

Our team (not at liberty to say which company unfortunately) moved away from Clojure back to Scala, or more accurately we built a couple of production services in Clojure, sunsetted them and haven't used Clojure since; the most vocal Clojure enthusiast moved on to another project and the rest of us were kind of meh on using it in the future after about a year of experience and went back to Scala (although certain things were quite fun and it was a fantastic learning experience and I would highly recommend at least getting familiar with REPL-based programming). It wasn't horrendous (and it's not like Scala is absolutely amazing for us), though maintenance was something of a pain point. We might use Clojure again, especially with some new blood who are Clojure enthusiasts. These days I'm less and less certain of what proactive role a language plays in team success. That is to say I think the arrow of causation is usually pointed in the wrong direction. A well-functioning, excellent team will, given sufficient latitude, converge on a language that suits a team well. This language is often different for each team. Introducing a "good" language is unlikely to save a team.