@Aaron thanks for your reply. Thanks for bringing up with Product Management. I as well raised now attention on a old feature around this to get feedback.
It helps when we post that new APIs will include a change (e.g. DMQ eligible default turns from false to true) to mention versions numbers. So as soon they are known it would be great to share so that customers know when to switch to new libs to get that changed.
Related to the news about copy message i am very happy to see but when i read the documentation it does not tell clear what happens with DMQ Eligible flag. As it turns from Main Queue (true) to DMQ (false) it must be switched back with copy back to true to avoid risk of message loss.
Message VPN-level Message Spool Administration (solace.com)
As well the copy only supports 1 message but customer need often following:
Copy all messages back (missing) And a combination of below filters: Filter on a specific message to copy back (now covered in copy command) Filter on time range to copy back (missing) Filter on # retry to copy back (which would require a DMQ retry count to be added and changed any time you push back to DMQ)