Is this a TCP/IP thread? Chances are you may be resending in which case the last sent will not fire.
I suggest, even for an outbound thread, you use Last Received Alert instead. The Last Received Alert will tell you when the last “SUCCESSFUL” send was. In other words you sent a message and got a reply.
I would like to expand on this question, as I have a similar issue. I am trying to put a last send or receive alert for message flow on an intermediary thread that receives charges once a day at a specific time. I have an inbound thread that recieves a file, and the intermediary thread breaks it up into separate HL7 messages. The intermediary thread then sends the messages along to a common or shared outbound thread for the charge (DFT) messages. I did reach out on the forum before, and received tcl procs to check for the file itself. I was just wondering if this could be done just via the Alert functionality.
If you are happy with your alert and just want it to fire more than once a day there is a quick simple partial solution we use to handle that situation.
Most alerts only fire once in the desginated window which sounds like an entire day in your case.
To reset the alert before that time is concluded schedule in cron to touch the $HCISITEDIR/Alerts/default.alrt file and that will reset your alerts for that site.
We touch all our defalut alert files in all our sites hourly during the day from 7AM-7PM, which has been a good balance for us.
If you are happy with your alert and just want it to fire more than once a day there is a quick simple partial solution we use to handle that situation.
Most alerts only fire once in the desginated window which sounds like an entire day in your case.
To reset the alert before that time is concluded schedule in cron to touch the $HCISITEDIR/Alerts/default.alrt file and that will reset your alerts for that site.
We touch all our defalut alert files in all our sites hourly during the day from 7AM-7PM, which has been a good balance for us.