> ## Documentation Index
> Fetch the complete documentation index at: https://help.texterchat.com/llms.txt
> Use this file to discover all available pages before exploring further.

# The Problem object

> A channel health problem record

problem describes a detected health issue on a connected channel account - e.g. send/receive impairment, rate limits, or verification issues. A problem without `resolvedAt` is still active.

<Info>
  Returned by: [List Channel Health Problems](/he/api-reference/channels/list-channel-health-problems) · [Channel health webhook events](/he/api-reference/webhooks/channel-health-events/channel-health-problem-created)
</Info>

```json Example problem object [expandable]  theme={null}
{
  "_id": "68cc1241bafffd81d455e788",
  "channel": "whatsapp",
  "accountId": "972586640430",
  "name": "whatsapp_business_has_limited_messaging_availability",
  "severity": "error",
  "impairedFunctionality": {
    "send": true,
    "receive": false
  },
  "message": "The Business has not passed business verification.",
  "instruction": "Visit business settings and start or resolve the business verification request.",
  "createdAt": 1758204481268,
  "startedAt": 1758204400000
}
```

## 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**          |