Re: Alarm stuck in "Async in progress" even after record processing is fine

[Jure Varlec via Tech-talk <tech-talk@aps.anl.gov>]

Hello Marco,

Which version of base are you using? There was an issue with AMSG not being cleared that was fixed in 7.0.9, so I suggest you try that before digging deeper.

Best,
Jure

On 11/21/25 16:19, Marco Filho via Tech-talk wrote:

Caution: This email originated from outside of Cosylab.

Hi, all.

I'm not sure if this is a bug or a feature: I have an IOC that hangs the record processing when the hardware disconnects. This causes the record to process over itself more than ten times, generating an "Async in progress" alarm message.

When the hardware finally reconnects, the record processing gets back to normal again, but the alarm message never disappears. AMSG and NAMSG keep displaying "Async in progress". ACKT is YES and ACKS is INVALID, although SEVR is already in NO_ALARM.

Shouldn't AMSG go to an empty string? Is there a proper way to acknowledge this alarm?

I found in the documentation:

"The ACKT field specifies if it is necessary to acknowledge transient alarms."

But I couldn't find how is this acknowledgment made.

Thanks for any help,

Marco