A reader is behind
Weik.io 2026.2Events have waited more than 15 minutes for an integration's reader, or the number waiting has grown at each check for 5 minutes. Video
Watch: Sending data to several destinations, 3:05
The video sends every new invoice to three systems through one channel with one reader per destination.
This part of the video couldn't be loaded.
| Kind | Severity | Who sees it |
|---|---|---|
reader- |
Warning | Everyone who can read the deployment |
What it means#
An integration that receives events from a channel is falling behind. Events wait for it longer than they should, so whatever it does with them happens late.
What raises it#
The problem shows when the oldest event waiting for the reader has waited longer than 15 minutes. It also shows when the number of waiting events has grown at each check for 5 minutes. Weik.io checks the readers every 30 seconds.
What to check#
See each reader with how far it has come:
$ weikio get readers --env <environment> --integration <project>/<integration>Check the integration’s state and errors:
$ weikio status <project>/<integration> --env <environment>How to fix it#
- When the reader is too slow for its events, give it more copies on more agents.
- When the reader fails events and retries them, fix the cause its log shows.
- When the waiting events no longer matter, skip them.
To skip the waiting events, run:
$ weikio reader skip <project>/<integration> --env <environment> --channel <channel>