A reader's backlog is at risk
Weik.io 2026.2A reader's oldest waiting event is getting close to the age at which the stream deletes it.
| Kind | Severity | Who sees it |
|---|---|---|
reader- |
Warning | Everyone who can read the deployment |
What it means#
The events a reader hasn’t handled yet are getting old enough that the stream may delete them before the reader gets to them.
What raises it#
The problem shows when the oldest waiting event is within 3 days of the stream’s age limit. It also shows when the stream uses more than nine tenths of its size limit while the oldest waiting event is more than half as old as the stream’s oldest event.
What to check#
See each reader with how far it has come:
$ weikio get readers --env <environment> --integration <project>/<integration>See the environment’s streams with their usage and limits:
$ weikio get streams --env <environment>How to fix it#
Before the stream deletes the events, use the fixes in A reader is behind to get the reader to catch up. A platform administrator can also give the environment’s events more room with weikio env set <environment> --events-bytes <size>. Use --runs-bytes instead for the runs of transfers and schedules, or --entity-events-bytes for entity changes.