An integration is failing
Weik.io 2026.2In the last 15 minutes, at least 5 messages and 5 % of a deployment's messages failed with no error handler to catch them. The problem is an error once half of them fail. Video
Watch: What a running integration is doing, 4:24
The video opens the logs and metrics of a running integration and follows its traces, in the CLI and in the admin UI.
This part of the video couldn't be loaded.
| Kind | Severity | Who sees it |
|---|---|---|
deployment- |
Warning, and an error from 50 % of the messages | Everyone who can read the deployment |
Its row in the problem list has a figure such as 42 of 310 failed in 15 min.
What it means#
Messages fail in a deployment’s routes with no error handler to catch them. A message that fails here didn’t reach where the route sends it, so the work it carries, such as an invoice or an order, wasn’t done.
What raises it#
The problem shows when at least 5 messages and at least 5 % of the deployment’s messages failed in the last 15 minutes. It becomes an error when half of them failed. For a deployment that started less than 15 minutes ago, the counts cover the time since it was deployed. Weik.io checks the problem every 15 seconds. The figure changes about every 30 seconds, because the copies send their counts that often.
When an error handler in the route handles a failure, for example by retrying it or sending it to a dead letter channel, the failure doesn’t count.
The detail shows the route with the most failures. You don’t see this problem on an installation set up without the hub’s metric store.
What to check#
See where the integration runs and in what state:
$ weikio status <project>/<integration> --env <environment>List the errors of the last 15 minutes, grouped by exception and route:
$ weikio logs <project>/<integration> --env <environment> --since 15m --top-errorsOpen the failed traces, which show the step that failed and every retry:
$ weikio traces <project>/<integration> --env <environment> --errors --since 15mHow to fix it#
When the cause is on the other side, such as an upstream that answers with errors or a server that refuses the connection, fix it there. The problem clears once the share of failures falls below the threshold. When a new version broke the route, roll back to the version that ran before while you fix it:
$ weikio rollback <project>/<integration> --env <environment>