DMQ Eligible Flag set on Publisher (violates pub sub principles)

Hi @Robert , how you doing? I’ve contacted a couple account people who should hopefully be in touch with you out-of-band. Sounds like you could use a meeting with our PLM. But to answer some of your questions:
There is feature work being done right now to provide more granular broker controls on DMQ Eligibility. There will be override capabilities added to both Guaranteed Endpoints (queues and TEs), as well as to Client Profiles, that will be able to supplant whatever the publisher set as the DMQe flag on each message. PLM didn’t give me a timeline though, but it design documentation is pretty much done.
I’ve asked about message copying enhancements, waiting to hear back.
OH! And I verified that the DMQe flag gets put back as true when copying a message back to the main/other queue. My steps:
Setup q1 with max-ttl set to 10 seconds, and respect-ttl = true Setup DMQ, with q1 pointing to it Publish message to q1 with DMQe = true After 10 seconds, message expires to DMQ Browse message in DMQ, confirm DMQe flag is not present Admin copy message back to q1 Consume out of q1, confirm DMQe flag is present again. Yup! If I don’t consume out of q1, message moves to DMQ again (now there are two, b/c it is a “copy” command). Hope that helps!