0
63

Written by

Scott Roth
Enterprise Application Development Consultant at The Ohio State University Wexner Medical Center
MOD
Follow
Question Scott Roth · Dec 1, 2025

Resend a single message based on Session ID

#HealthShare #InterSystems IRIS for Health #Health Connect #InterSystems IRIS #System Administration

I am working on building out a Workflow task that captures errors in mapping to specific tables. Within the Workflow task, I would like to give the owner of the task the ability to resubmit message once the mapping has been corrected. Is there a way to do it in a similar fashion to pulling up the Trace ie...

EnsPortal.VisualTrace.zen?SESSIONID=#(%task.%FormValues.GetAt("MsgHdrID"))#" target="_blank">View Message Trace

Is there a one liner that could be called to resubmit the MsgHdrID (Session ID) from its source to post it again?

Product version: IRIS 2024.2
$ZV: Version HealthShare Provider Directory 2024.2.0 Build: 1009 [HealthShare Modules: Core:28.0 + Provider Directory:28.0] - IRIS for UNIX (Red Hat Enterprise Linux 8 for x86-64) 2024.1 (Build 267_2_24113U) Wed Jul 2 2025 16:36:55 EDT [Core:28.0|Provider Dir
Discussion (1)2
Log in or sign up to continue

Comments

DC AI Bot · Dec 1, 2025 Bot

Resending messages based on a Session ID or Message ID can be handled programmatically or via the Management Portal depending on your requirements:

  1. Resending Messages Programmatically: You can use methods like ResendDuplicatedMessage() or ResendMessageBatch() by specifying the required parameters to filter messages. For example, if you know the exact message IDs or need to filter by Session ID, use:

    set tSC = ##class(Ens.MessageHeader).ResendDuplicatedMessage(MsgHdrID)

    This ensures the message associated with MsgHdrID is resent from its original source [1].

  2. Using Management Portal: Navigate to Interoperability > View > Messages and find the relevant message. From there, you can click Resend Messages to resubmit it. For advanced options, you can edit the message before resending or assign it a new target [1][2].

  3. Handling Errors and Debugging: Messages can include information about their session, enabling efficient filtering and identification of problematic mappings. The SessionId property is consistent across all messages in a session and corresponds to related workflows [3][1].

  4. In scenarios where you need automated solutions for resending failed messages, you might deploy broader approaches such as scheduled tasks or SQL filters for batch processing [4].

References: [1][4][2][3]

Sources:

0