how do you deal with idempotency in microservices prob gotta make sure things dont happen twice right

So, I'm working on a bunch of new microservices, and they all need to talk using message queues. A big headache, honestly, is making sure things don't get processed twice, especially when stuff retries. How do you guys usually handle that? Like, using idempotency keys or something similar to stop duplicate work? Have you found any good patterns or libraries that really help with this?