Specific error code for messages that are manually aborted by a user

Question

Question

Lewis Houlden · Aug 26, 2021

#Business Process (BPL) #Error Handling #Health Connect #InterSystems IRIS for Health

New to Health Connect so please forgive me if this is a stupid question! Is there a specific error code returned when a user initiates an abort from the jobs tab of the business host? I want to be able to treat the Abort as Completed due to our complex business process. Currently, hitting abort just retries the message to the same business operation. Want I want to do is provide the error code used by the Abort (if there is one) and treat it as OK

Thanks in advance.

Product version: IRIS 2019.1

Discussion (4)1

Log in or sign up to continue

Lewis Houlden · Sep 1, 2021

Thank you @Vic Sun @Eduard Lebedyuk and Robert for all responding to this query. I've realised that our Business Process were set to E=R which is was causing it to re-attempt immediately after abortin the message from the operation. As the operations are retry indefinitely unless aborted, we've settled for E=D, which means we can then abort from the process. Thanks again. Lewis

0 0

score 0 · Answer 1 · 2021-08-26T10:27:39-04:00

Hello Lewis,

In my experience, aborting doesn't retry a message. I wonder if something in your production is resending the message? Do you see anything in the logs that speak to what is happening?

This may be worth opening a WRC about - if you do, I would be interested in hearing what you end up finding out.

score 0 · Answer 2 · 2021-08-26T12:00:00-04:00

@Lewis Houlden
If you stop a process from the Management portal you have the option to launch an <RESJOB> error in $ZE
this allows you to clean out the message that triggered your process.
If not, the triggering message remains unprocessed in the queue.
Which results in the retry you see.

score 0 · Answer 3 · 2021-08-27T05:18:00-04:00

Eduard Lebedyuk · Aug 27, 2021

You need a Reply Code Action, E=S or something more specific.

0 0