Engine

Covers Engine 2.0.0

argus/events/history-refresh

Tells history consumers to refresh after a large mutation batch or bounded publication overflow.

  • Category: Events
  • Direction: Server → clients

Delivery

Published when a queued mutation batch exceeds the ARGUS per-event publish limit, or when bounded publication admission loses messages. Clients refresh from current state and history.

Payload

FieldTypePresenceDescription
countintegerAlwaysNumber of event IDs in a large batch; zero for overflow.
reasonstringConditionalPresent as overflow when publication admission loses messages.
dropped_messagesintegerConditionalNumber of publication messages lost since the prior overflow refresh; present only for overflow.