Announcement

Collapse
No announcement yet.

Error messages are not pruning

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Error messages are not pruning

    Hello.

    Recently, in our mirth production enviroment, we have changed our channels configuration to stop allow message archiving, so the error messages can be pruned after 30 days. The pruner runs everyday at 4:00 am, but the error messages are not being pruned, we still have error messages from the begining of the service.

    Mirth version is 3.7.1

    Pruner conf:
    pruningConf.png


    Channel conf :

    ChannelsConf.png


    We also have tried turning prune Events into "yes" in pruner config, but it did not work.

  • #2
    Errors never prune in 3.7.1. I think 4.0 and later added that option. Check release notes.
    Diridium Technologies, Inc.
    https://diridium.com

    Comment


    • #3
      In 4.0.1 for sure:

      2022-08-03_15-14.png
      Diridium Technologies, Inc.
      https://diridium.com

      Comment


      • #4
        I had a similar issue. Although it was set to prune it couldnt because it couldnt find the threshold to prune as it was timing out as it was never pruning in the first place and data built up. The Only way was to export and import same channel back

        Comment

        Working...
        X
        😀
        🥰
        🤢
        😎
        😡
        👍
        👎