A deployment matches nothing
Weik.io 2026.2A running deployment's routes refer to something its project doesn't have in the environment, such as a deleted channel, so the deployment's next start fails. Video
Watch: The channel: one integration publishes, another reacts, 3:49
The video has one integration publish to a channel and another react to it.
This part of the video couldn't be loaded.
| Kind | Severity | Who sees it |
|---|---|---|
deployment- |
Error | Everyone who can read the deployment |
What it means#
A running deployment’s routes refer to something that its project doesn’t have in the environment:
- A channel
- A file transfer
- An entity type
- A schedule
One cause is a channel that someone deleted or renamed. If the channel was renamed, the copies that run now keep working. If it was deleted, they keep running, but what they send to it is lost. Either way, their next start fails.
What raises it#
Each time you list the problems, Weik.io checks again. The list has one row for each missing name, whichever way a route uses it. It also has one row for a missing channel that an API deployment’s webhook publishes to.
A name that a route builds in an expression, or that comes from a project’s kamelet, doesn’t raise this problem. When such a name is missing, the integration fails when it starts instead.
What to check#
List the problems with their details, which show what is missing:
$ weikio problems --env <environment>List the project’s channels:
$ weikio get channels --project <project>List the environment’s entity types:
$ weikio get entity-store-policies --env <environment>How to fix it#
Create what the route refers to, or publish a version of the integration that refers to a name that exists:
$ weikio channel create <project>/<channel>
$ weikio entitystore policy set <project>/<type> --env <environment>