resolvedAt is still active.
Returned by: List Channel Health Problems · Channel health webhook events
Example problem object
Identity
| Field | Type | Description |
|---|---|---|
_id | string | Unique ID of this problem record in Texter |
channel | string | Which messaging channel this problem refers to (whatsapp, messenger, …) |
accountId | string | The affected account ID in Texter (same value as chatChannelInfo.accountId on messages) |
Classification
| Field | Type | Description |
|---|---|---|
name | string | Machine-readable problem code - a stable identifier for the issue type (1-100 chars) Example: whatsapp_app_id_error |
caseId | string | Provider / Meta case reference if available (32-128 chars). Problems sharing name + caseId are the same ongoing incident |
severity | string | error or warning |
Impact & guidance
| Field | Type | Description |
|---|---|---|
impairedFunctionality | object | Map of impacted capabilities to booleans (true = impacted). For WhatsApp mainly send and receive; other feature keys (attachments, templates, …) can appear Example: {"send":true,"receive":false} |
message | string | Human-readable explanation of the issue |
instruction | string | Recommended remediation. Not present on all problems |
Lifecycle
| Field | Type | Description |
|---|---|---|
createdAt | number | When this record was created (epoch ms) |
startedAt | number | When the issue actually started, if known - can be earlier than createdAt |
resolvedAt | number | When the issue was resolved (epoch ms). Missing = still active |