Message Purging Task Not Working as Expected

Question

Question

Ali Chaib · Nov 2, 2023

Hello Intersystems Community,

I'm currently facing an issue with message purging in my Healthcare environment, and I'm seeking your valuable insights and guidance to resolve it.

I've configured a purge task to delete messages older than 30 days, and when I run this task immediately, it doesn't delete anything,

I changed the 'Run task as this user:...', I thought it could be an access issue.. But nothing happened, I even changed the priority, same thing..

however when I uncheck the "Keep Integrity" option, it cleared all messages, regardless of the retention period!!.. So can someone please help me to understand what's going on?

Example:

Product version: IRIS 2022.1

Discussion (4)2

Log in or sign up to continue

Ashok Kumar · Nov 3, 2023

Basically you should keepIntegrity enabled. Otherwise it will delete all the messages regardless of whether processed or not processed.
Select "All types" in Type to purge.
You can enable the " Open output file when task is running? " and provide the file location.
Once the process is completed or Errored you can check the Ens_Util.Log to get some additional information.

Can you try the above steps.

0 0

score 0 · Answer 1 · 2023-11-02T11:33:52-04:00

You need to select the BodiesToo option(whenever the message header details the body also deleted) to delete the messages from the database

score 0 · Answer 2 · 2023-11-03T07:54:54-04:00

I'm sorry, I forgot to mention that I did that too.. And it doesn't delete the messages

As I mentioned above, the only time it delete the messages is when I uncheck the "Keep Integrity" option, however it delete everything! without respecting the retention period

score 0 · Answer 3 · 2024-07-25T09:22:26-04:00

TL:DR- Aborted queued messages to purge them.

I had the same problem trying to purge our development namespace so we could flush it clean for fresh unit test messages.

Messages still in progress will not be deleted. That means if there is a single message queued on one of the interfaces, all messages related to it will not be purged. Abort the queued message, and purge will work.

For example, one of our ADT messages goes to 15 different interfaces. One of the 15 is disabled and queued the message. That locks all 15 messages from being purged as technically, the production isn't fully resolved.