Problems

Weik.io 2026.2

Problems Weik.io raises, with a page for each that says what raised it and how to fix it.

On this page

Integrations and deployments
APIs
File transfers
Backups
Access
Agents
The hub
Telemetry and audit
Events
Certificates
See also

A problem is something that needs attention now, such as an integration whose messages fail, an agent that went offline or a certificate that ends soon. The admin UI counts problems under Needs attention on Home and lists them on Observability and on the record’s own page, and weikio problems lists the ones you may see with a command that shows more about each. Each problem in the tables below has a page that says what raised it, at which threshold, and the commands that fix it.

Some problems come from the hub’s metric store, and some only platform administrators see. Each page says which. Health and problems describes the Health page and how problems clear.

Terminal

$ weikio problems --env production

Find a problem by its kind or title

Integrations and deployments#

Problem	Kind	Severity
An integration is failing	`deployment-messages-failing`	Warning or error
An integration restarts in a loop	`deployment-restarting`	Error
Memory grows day after day	`deployment-memory-growing`	Warning
An integration stopped handling messages	`deployment-stalled`	Warning
No agent serves the deployment	`deployment-no-agent`	Error
A deployment runs behind its version	`deployment-version-behind`	Warning
A single-copy deployment has no leader	`deployment-no-leader`	Error
A single-copy deployment has two leaders	`deployment-two-leaders`	Error while both copies lead, then a warning
The leader keeps changing	`deployment-leader-changing`	Warning
A deployment matches nothing	`deployment-names-nothing`	Error

APIs#

Problem	Kind	Severity
An API fails on the server’s side	`api-failing`	Warning or error

File transfers#

Problem	Kind	Severity
A transfer run failed	`transfer-failed`	Error

Backups#

Problem	Kind	Severity
A backup is overdue	`backup-overdue`	Error
A backup copy failed	`backup-copy-failed`	Error

Access#

Problem	Kind	Severity
Two-factor sign-in is off	`two-factor-off`	Warning

Agents#

Problem	Kind	Severity
An agent is offline	`agent-offline`	Error
An agent never reported	`agent-never-reported`	Warning
An agent runs an older bundle	`agent-bundle-behind`	Warning
An agent’s disk is low	`agent-disk-low`	Warning or error
An agent’s memory is low	`agent-memory-low`	Warning or error
An agent’s revocation is pending	`agent-revocation-pending`	Error

The hub#

Problem	Kind	Severity
A gateway instance is offline	`apim-instance-offline`	Error
A backend node is offline	`backend-node-offline`	Error
A hub server is cut off	`hub-server-cut-off`	Error
Message storage is off	`message-storage-off`	Error
A store is filling up	`store-filling`	Warning or error, by store

Telemetry and audit#

Problem	Kind	Severity
Telemetry was lost on the way	`telemetry-dropped`	Warning
Telemetry is waiting on a hub server	`telemetry-waiting`	Warning or error
Audit records are waiting	`audit-records-waiting`	Warning or error

Events#

Problem	Kind	Severity
Dead letters are filling up	`dead-letters-full`	Warning
A reader is behind	`reader-behind`	Warning
A reader’s backlog is at risk	`reader-backlog-at-risk`	Warning
A reader has dead letters	`reader-dead-letters`	Warning
A reader lost events	`reader-lost-events`	Error
A reader has no consumer	`reader-no-consumer`	Error
A reader isn’t durable	`reader-not-durable`	Warning
A reader isn’t receiving	`reader-not-receiving`	Error
A reader needs a restart	`reader-restart-needed`	Warning

Certificates#

Problem	Kind	Severity
A certificate is expiring	`certificate-expiring`	Warning or error
A certificate expired	`certificate-expired`	Error
A certificate request is failing	`certificate-request-failing`	Warning or error