InterSystems Ideas

Have an idea, suggestion, or something that doesn’t work as expected in InterSystems products or services? Share it here on the InterSystems Ideas Portal.

The Ideas Portal is where community members can propose improvements, report bugs, and help influence the product roadmap across InterSystems products and the overall developer experience. 22% of submitted ideas are implemented by InterSystems or members of the Developer Community.

💡 Ideas and bugs are both welcome, no matter how big or small. You can submit feature requests, usability improvements, workflow suggestions, and bug reports. Whether you’re an experienced expert or just getting started, your fresh perspective is valuable.

🛠️ About bugs and fixes. If you have access to InterSystems WRC, please submit bugs there for immediate action. Bug reports submitted through the Ideas Portal are reviewed and tracked, but do not guarantee immediate resolution.

Start by sharing what could be better - the community and our teams will help take it from there.

Add a new idea Subscribe
Status Needs review
Categories InterSystems IRIS Interoperability
Created by Stephan Mohr
Created on Jul 28, 2026

RELATED IDEAS

Additional filter for purging messages

It should be possible to exclude messages with an error status from being deleted when running the purge task or methods like Purge() in Ens.Util.MessagePurge, so they can be resend. A customer reports that sometimes these failed messages are purged too early before the errors have been reviewed.

  • ADMIN RESPONSE
    Jul 28, 2026

    Thank you for submitting the idea. The status has been changed to "Needs review".

    Stay tuned!

  • Post comment
  • Attila Toth
    Aug 6, 2026

    Totally agreed! In large systems, with millions of messages flowing through the system, finding errors is not simple and may not happen within the normal retention period of messages. If erroneous sessions could be kept for a longer amount of time (let's say: a separate background task instance would purge them, only after a longer period), that would make retrospective investigation much simpler, while the storage space used for preserving historical messages could be kept under control.

    Reply
  • Andreas Heinbokel
    Jul 29, 2026

    for practical use of InterOp: user is interested in failed operations. everything running fine is not relevant. these must be kept for repeat or further examination. good idea.

    Reply