An integration stopped handling messages
Weik.io 2026.2A running deployment has handled no message for 15 minutes or three times its longest gap of the previous week, whichever is longer.
| Kind | Severity | Who sees it |
|---|---|---|
deployment- |
Warning | Everyone who can read the deployment |
The row’s figure gives the numbers in a few words, such as no message for 40 min.
What it means#
A running deployment has stopped handling messages for longer than it ever waited before. Its process is up, but nothing passes through its routes.
What raises it#
The deployment is running, its agent is online and no message has gone through it for longer than 15 minutes or three times the longest gap between messages in the previous 7 days, whichever is longer. It’s judged only after a day of message history, so a route that runs at night isn’t stalled at noon and a deployment that never took a message isn’t stalled at all. While the sites of its copies are offline or still sending telemetry they kept, the problem waits, because the messages may not have reached the hub yet. The problem needs the hub’s metric store, which every installation has unless it was set up without one.
What to check#
Check the state of each copy:
$ weikio status <project>/<integration> --env <environment>Read the latest log lines:
$ weikio logs <project>/<integration> --env <environment> --since 1hChart the messages to see when they stopped:
$ weikio metrics <project>/<integration> --env <environment> --name messages --since 24hHow to fix it#
Check what feeds the route: a source system that stopped sending, a queue or folder that’s empty, a scheduler whose cron changed, or a consumer that lost its connection without failing. When the route itself hangs, restart it:
$ weikio restart <project>/<integration> --env <environment>