We consume the Filing History streaming API and have noticed that a number of accounts (AA) filings which appear in the filing history (and via the REST API) never come through on the stream.
We’re confident they aren’t being dropped on our side — the event.timepoint sequence we receive is fully contiguous with no gaps, so we aren’t skipping events.
The gap looks specific to accounts filings: for the same companies, other event types (e.g. CS01, DS01) arrive on the stream fine around the same time.
This affects several hundred companies. A few examples where the latest accounts filing is in the filing history but absent from the stream:
- 11908649
- 11757179
- NI641404
Is this a known issue with the streaming pipeline?
Thanks