You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the OnDelay case, this may be because state is ActiveLatched. We need to guard against OnDelay as well if NotActive, and perhaps also when Latched. This gets confusing as you start to mix and match overrides: JeffersonLab/jaws#24
Effective processor does not appear to latch on NoActivation. More investigation needed. Perhaps on startup some channels take too long to connect to EPICS and result in ChannelErrors, which eventually resolve to NotActive. In this case the issue might be the audit logger is capturing the wrong state: expected would be type ChannelError, not type NotActive.
The unexpected part is the activation type. Perhaps the stream join on override isn't grabbing the updated activation type? Starting from empty history a fresh restart results in the following notification history examples:
The special NotActive activation placeholder appears to be triggering a Latch:
The text was updated successfully, but these errors were encountered: