message queues for decoupling or orchestration?

Hey all, been thinking about how we use message queues like RabbitMQ or SQS in our microservices. We use them a lot for simple decoupling - service A fires off a message, service B picks it up and does its thing. But I'm seeing more complex workflows where a message queue seems to be acting more like a central orchestrator, with services reacting to messages and sending new ones to manage the overall flow. Does anyone else do this? What are the pitfalls of using queues for orchestration versus pure decoupling? Curious about your experiences and best practices here.