When do message queues just cause more headaches than they solve in system design?

I've been using message queues a bunch lately, mostly for microservices. They're good for letting different parts of a system talk without being super connected and for handling lots of tasks. But man, they can also add a lot of extra work and make things tricky, especially with stuff like dead-letter queues, retries, and making sure things only happen once. For someone new, or on smaller projects, it feels like a really hard thing to learn. So, I'm wondering, when do people think message queues, even with all their good points, actually become more trouble than they're worth? Are there certain project sizes, or maybe team skills, or even ways of setting up your system where the headaches outweigh the good stuff? I'm not just talking about the obvious, like 'dont use them for simple communication.'