Use **Channel Health** to identify queued work and retained failures for one property, then choose the appropriate investigation screen.

## Before you start

You need access to the property in ChannelRUSH. This report reads stored configuration and processing evidence. It does not contact a channel to check its current rates or availability, resend requests, or change settings.

## Run the report

1. Select the property in the property selector.
2. Open **Reports → Diagnostics → Channel Health**.
3. Choose a **Channel**, or leave **All property channels** selected.
4. Set **Terminal request history (days)** to a value from **1 to 90**. The default is **30**. This includes completed or failed requests created within that period. Current pending and processing work can be older than the selected period.
5. Choose a **State**, or leave **All states** selected.
6. Choose a **Flow**, or leave **All** selected. The flows distinguish outbound inventory, inbound PMS inventory, inbound PMS monitoring and reservation delivery.
7. Click **View report**.

![Channel Health filters showing channel, terminal history, state, flow and View report.](https://support.channelrush.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBb29CIiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--30c90a0957fea7d8c533fbdb47f7dbe99edb8685/channel-health-filters.png)

To change the report, expand **Filters**, adjust your selections and click **Update report**. Running it again reads current evidence; it does not retry any work.

## Check the result

Confirm the property name and extraction timestamp above the table. Each row describes a **channel and flow**, not an individual request. Channels can appear from stored settings or retained request history, including channels not offered in the main Channel selector.

The totals above the table cover the full filtered result. The web table shows at most **100 rows per page**; channel-heading subtotals describe the rows on that page. **CSV** exports the full filtered selection, not only the visible page. Each load or export reads again, so processing activity can change the values between them.

### Read the evidence

| Column or state | What it tells you |
|---|---|
| **Pending / Processing** | Work currently waiting or being processed. |
| **Unresolved failures** | Retained failed requests that still meet this report's unresolved-failure rules. |
| **Oldest in queue (h)** | Age of the oldest pending or processing request, in hours. This is queue age, not delivery latency or a promised completion time. |
| **Known retries** | Recorded extra attempts for included outbound inventory requests. An unavailable value is not zero. |
| **Latest outcome / Last seen** | The latest retained request state and its edit time; monitoring instead uses a recorded heartbeat. Read the displayed time-zone offset. |
| **Enabled / Setup** | Stored configuration flags, not proof that the remote channel is synchronized. |
| **Idle** or **Idle / no retained activity** | No current failure or queue takes precedence, and the applicable retained evidence is successful/reviewed or absent. A quiet connection is not automatically failing. |
| **Monitoring evidence** | A heartbeat was recorded. This does not establish current inventory freshness or a monitoring SLA. |
| **Unknown / —** | Evidence is unavailable or not established. Do not read it as success or zero. |

A **Failed requests** state takes precedence over pending work and disabled settings. Read the counts and configuration columns together rather than relying on State alone.

## Investigate without resending

Use the links beneath the report:

- **Inventory Settings / Channel Settings** opens the settings report.
- **Inventory processing detail** opens the inventory processing summary.
- **Reservation delivery detail** opens Reservation Delivery Failures.

These links preserve the property, not this report's channel, state, flow or history filters. Check the destination's scope before comparing counts. Reservation Delivery Failures initially uses its own **1-day** lookback. Opening a detail screen does not itself resend a request.

An unrelated successful request does not clear an earlier failure. For channel reservation delivery, a later success must match the same reservation version and destination channel. Do not resend solely to remove a historical failure from this report.

## Common problems

- **No matching rows:** Your filters may exclude the available evidence. Return to **All property channels**, **All states** and **All**, then run again. No matching rows is not proof of successful delivery or complete telemetry.
- **Disabled with pending work:** Work remains queued while the flow is disabled. Inspect the settings and processing detail; contact support before changing enablement or resending.
- **Unsupported, Not set up or Unknown:** Review the flow and stored setup before treating this as a delivery failure. If the expected setup and evidence disagree, contact support.
- **“Select 1–90 days of terminal request history.”:** Correct the history value and run again.

If the evidence still does not explain the problem, send support the property, channel, flow, filters, extraction time with its offset and relevant error text. Do not include passwords or payment details.

## Related

- [Track and recover reservation delivery failures](https://help.channelrush.com/hc/channelrush/articles/reservations-delivery-failures)
- [Review channel mapping coverage](https://help.channelrush.com/hc/channelrush/articles/mapping-coverage)
