Lost events

Because the controller is a fixed capacity resource, under extreme conditions, it is possible for event data to be lost. Event data can be lost when:
  • A step is run and then the step is run again so soon after the first run that the step’s event buffers are overwritten.
  • The event log within the controller overwrites event data that has not yet been published. This can happen because the <SEQMGR> Event Client Service is not subscribed for too great a time, or the sustained number of events generated exceeds the rate events can be published.
In both cases a
Lost Event
record is written to the .EVT file and the event database (if configured) to signal that at least one event has become lost.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.