Find the requests behind a property's rate, availability or restriction change, read their processing results, and choose a safe next action.

## Before you start

- Sign in with access to the property you want to investigate. Select that property in the application’s property selector before opening **Updates → Status**. The heading is **Update Status**.
- This page shows outbound inventory update requests. It is not the reservation-delivery screen or a live comparison with a channel's current inventory.
- Searching does not resend inventory. **Search** applies filters; **Go** runs the selected request action. Do not use Go to refresh results.
- **Retry**, **Archive** and **Un-Archive** require an update permission for rates, availability or restrictions. Viewing the page does not grant those permissions. The public demo login can search but cannot run these actions or open the support form through Go.

## Find the affected requests

1. Select the affected property in the property selector.
2. Open **Updates → Status**.
3. Select the destination **Channel**, if known.
4. Select **Status**, or leave **All** if you are following a request whose status may change.
5. Select the relevant **Room Type**, **Rate Plan**, **Sent By** or **Source**, if needed.
6. Click **Search**.
7. Check the retained selections, **Filtered by** summary and matching request rows.

The page loads requests when opened. Changing a filter does not load new results until you click **Search**. **Clear Search Filter** removes the search criteria, not the saved requests.

![Search Filters with status, channel, product, origin, data-type, archived, stay-date and timestamp controls.](https://support.channelrush.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBcjRCIiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--cd98233728bf3fc426d5f15ea27425aaeb95dc68/update-status-filters.png)

*At narrower widths, the same controls stack vertically. The selected property is in the application’s property selector, outside this filter card.*

Use **»** and **«** to move through results, normally 50 requests at a time, with newer request IDs first. Paging retains the applied search criteria. Click a filter's remove control in **Filtered by** to remove that filter group and reload from the beginning. Removing the Data group removes all its data-type selections together.

### Find a known request ID

1. Select the correct property.
2. Click **Clear Search Filter** to start without conflicting criteria.
3. Enter the numeric **ID** from the request in **Request ID**. This is not a reservation number.
4. Leave **Rates**, **Availability** and **Restrictions** unticked, or tick all three.
5. Click **Search**.
6. Confirm the returned row has the intended ID.

A Request ID search overrides most ordinary search filters, including status, channel, products, source, sender, date matching and the normal archived exclusion. However, a partial Data selection can still hide it, and reversed date ranges can prevent the search. The Request ID summary does not display those remaining constraints. Clear the ID before returning to an ordinary filtered search.

## Read a request and check the result

The **Channel / Room Type / Rate Plan** column identifies the destination and product. The **Updates** column shows the stored request's affected dates, applicable weekdays and values. Those dates are different from when the request was created or processed.

![A stored demo request showing a room and rate plan, rates, Stop Sell, Min Nights, Successful status, attempt count, request ID and timestamps.](https://support.channelrush.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBcjhCIiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--84e3674770ade8eea69c955977f40a1ab2075d37/update-status-request.png)

*This is historical request data. Successful processing is not a fresh check of the channel's current rates or availability.*

Read the information beneath the requested values:

- **Status:** the recorded processing state. Read any accompanying message, not only the colored marker.
- **Attempts:** the processing attempt count, not a count of confirmed successful deliveries.
- **Source and sender:** where the request originated. For example, **UI Quick** in the filter appears as **UI - Quick** in a result. PMS-related requests can identify a PMS channel rather than a person.
- **Archived:** when shown, the request is marked archived. This is separate from its processing status.
- **ID:** the internal inventory request identifier to use for a precise search or support investigation.
- **Created:** when the request was created.
- **Last Run:** its recorded processing/edit time. Queuing a retry also changes this timestamp; a recent Last Run alone does not prove a completed send.
- **Logs:** opens the available attempt log in a new tab. This link is not shown for every request. Missing or empty logs do not prove success or failure. See [Inspect an inventory update request log](https://help.channelrush.com/hc/channelrush/articles/update-request-log).

Created and Last Run use your user's time zone, shown beside the timestamps. Log message timestamps use **UTC**. Preserve the relevant zone when reporting a problem.

### Status reference

| Status | What it tells you |
|---|---|
| **All** | No status restriction. Use it when following a request through state changes. |
| **Pending** | Waiting for processing; not confirmation of channel acceptance. |
| **Processing** | Processing is in progress. Investigate before requesting another attempt. |
| **Successful** | ChannelRUSH recorded successful processing. This does not establish that every current channel value matches your intended inventory. |
| **Unsuccessful** | Processing did not succeed. This filter includes failed processing requests as well. Read the message and investigate the cause before retrying. |

For a request you are following, search again by ID or with **All** status and inspect the latest status, message and logs. Disappearing from an unsuccessful-only search can mean its status changed. An empty list does not establish delivery. When channel confirmation is needed, check the intended product, dates and values in the channel as well.

## Filter reference

Filters normally narrow one another: the matching request must satisfy each selected filter. A Request ID search has the exceptions described above.

### Destination, product and origin

| Field | What it does |
|---|---|
| **Status** | Selects a processing state. All leaves status unrestricted. Unsuccessful includes failed processing results. |
| **Channel** | Selects the destination channel, not the PMS or workflow that originated the update. All leaves the destination unrestricted within the selected property. |
| **Room Type** | Matches the property's standard room type. It is not a search for a channel room code. |
| **Rate Plan** | Matches the property's standard rate plan. A result can show the corresponding channel rate-plan name instead. |
| **Sent By** | Matches the user associated with a request. Available choices can include **PMS - …** entries as well as property users. All leaves the sender unrestricted. |
| **Source** | Matches the originating workflow. For example, choose UI Quick to investigate a Quick Update. It is independent of Channel. |
| **Request ID** | Finds a specific internal inventory request. Use the known-ID procedure above rather than combining it with unrelated criteria. |

Source choices include **PMS**, **UI Daily**, **UI Detail**, **UI Quick**, **UI Calendar**, **UI Bulk Import**, **Channel Refresh**, **Master Refresh**, **PMS Refresh**, **Reservation Adjustment**, **Office Hours** and **Future Limit Loader**. These identify the origin, not a separate delivery-success state.

### Data and archived requests

| Control | Meaning |
|---|---|
| **Rates** | Matches requests with recorded net/sell rate changes or additional rate parameters. |
| **Availability** | Matches recorded allocation or **Stop Sell** changes. Stop Sell belongs here, not under Restrictions. |
| **Restrictions** | Matches recorded arrival/departure closures, minimum/maximum nights, through-night restrictions or cutoff-day changes. |
| **Include Archived Updates** | Includes archived and nonarchived requests. Unticked normally excludes archived requests. This checkbox only changes visibility; it does not archive anything. |

With none or all three Data controls selected, there is no data-type restriction. Selecting one or two matches **any** selected type, not necessarily every selected type. The whole request is displayed, including its other values. Older requests without recorded change-type information can disappear under a partial selection; use none or all three when locating a known request. Channel-specific custom parameters alone are not one of these three data groups.

### Stay Dates

Use **Stay Dates** for the dates whose inventory the request affects, not the day you sent it.

- Enter both dates to find requests whose affected-date span overlaps that range, including spans beginning earlier or ending later.
- Enter only the first date to find requests ending on or after it.
- Enter only the last date to find requests starting on or before it.
- Enter the same date at both ends to find requests covering that date; requests explicitly excluding its weekday are excluded.
- Leave both blank for no stay-date restriction.

For a multi-day range, inspect each request's displayed weekdays as well as its date span. Span overlap alone does not establish that every night in your search is included.

### Date and Time

Use **Date and Time** for when the request was created or last processed/edited. This range is independent of Stay Dates, so you can use both together.

1. Choose **Created** or **Last Run**.
2. Enter the first and/or last date using the displayed date format.
3. Enter an optional time beside each date if you need a narrower window.
4. Click **Search**.

**Created** is the default timestamp choice. **Last Run** includes the recorded edit time changed by a retry; it is not proof of a completed channel send.

Times use your user's time zone, identified beneath the controls. Without a time, the entire date is included: a multi-day range includes the whole final day. With a time, the starting minute is included and the entire final selected minute is included. A time without its accompanying date does not narrow the search. Leave both dates blank for no timestamp restriction.

For example, use Stay Dates for a weekend whose rates are wrong, and Created for the day your team submitted the change. These answer different questions and can be combined.

If **The End Date cannot be before the Start Date.** or **The last stay date cannot be before the first.** appears, correct the relevant range and click Search again. Do not interpret the error-state list as a completed search.

## Requested values reference

The values shown depend on what is stored in the request and supported by its channel. This screen is a viewer, not an inventory editor.

| Value | Meaning in the stored request |
|---|---|
| **Sell Rate / Net Rate** | Requested amounts and currency. An asterisk marks the selected rate type. |
| **Allocation** | Available-room quantity carried by the request. |
| **Stop Sell** | Whether sales are closed or opened for the request's scope. |
| **CTA / CTD** | Closed to arrival / closed to departure. |
| **Cut Off Days** | Advance-booking cutoff value. |
| **Min Nights / Max Nights** | Minimum/maximum stay values. |
| **Min Nights Through / Max Nights Through** | Through-stay restriction values. |
| **Additional rate/channel parameters** | Channel-specific values shown when present and supported. |

A missing field is not automatically zero, No or a removal instruction. **VRT** identifies a virtual room type. **[BLANK / NOT SET]** indicates missing product-name information: check the setup before deciding to retry.

## Choose a safe next action

The dropdown and **Go** controls above and below the results operate on the checked requests. The table-heading checkbox selects the requests on the **current page**, not every matching request across other pages. This page has no all-matching Retry or Archive action.

First finish your search, inspect the rows, and tick the intended requests. Changing a search field without clicking Search does not replace the rows you are selecting. Do not assume Go will show a second confirmation before changing requests.

### Send evidence to support

1. Find the affected requests with **Search**.
2. Tick their checkboxes.
3. Select **Send To Support**.
4. Click **Go** to open the support form.
5. Review the selected request details, enter an appropriate **Subject** and describe the problem in **Message**.
6. Click **Send** when you intend to contact support, or **Cancel** to leave without sending.

Opening the form does not send the message. Include the property, channel, affected inventory dates, request IDs, action time/time zone, expected result and relevant error text. Never include passwords, payment details or unnecessary guest data.

The support message includes generated request details, not an automatic attachment of every raw attempt log. Its confirmation does not mean the inventory problem is resolved or guarantee that a person has received it. If the send outcome is unclear, check before sending the same message repeatedly. Returning to the list can restart on its first page; recheck the criteria and selected requests.

### Retry

**Retry can also requeue later overlapping requests for the same property, channel and mapped products.** Those requests need not share your selected status or source. Processing can use current settings. If you are unsure which requests will be affected, contact support before retrying.

1. Read the error/message and resolve the underlying issue, or obtain support's recommendation.
2. Search again and check that the request is not already Processing and its affected dates are still relevant.
3. Tick the specific requests you intend to retry.
4. Select **Retry**.
5. Click **Go**.
6. Search again by the known IDs or with **All** status.
7. Inspect the resulting status, message and logs before considering another attempt.

Requests requeued for retry become Pending and unarchived, and their previous message is cleared. The attempt count is not reset. Past-only requests may no longer be eligible. **All requests marked to be retried** confirms the retry action, not that every selected record changed or that the channel accepted the inventory. Do not repeat Retry merely because acceptance is not yet confirmed.

### Archive and Un-Archive

**Archive is not cancellation.** It does not stop a pending send, prevent automatic retries, reverse inventory or delete the request. Automatic retry can unarchive it again. Archiving changes shared request state, not a private viewing preference.

1. Search for the requests and review their status and dates.
2. Tick the intended rows.
3. Select **Archive** or **Un-Archive**.
4. Click **Go**.
5. Find the known request IDs, or enable **Include Archived Updates** and click **Search**.
6. Check whether the Archived indicator is present as expected.

Un-Archive removes the archive flag; it does not itself request a retry. Neither action changes the processing status or establishes that a delivery problem has been resolved.

## Common problems

- **No requests appear:** filters may exclude the request. Clear the search, use a known Request ID, or broaden the relevant status, date, product, source, sender, archived and Data choices. If it remains missing, contact support with the property, channel, dates and action time; do not resend inventory solely because the list is empty.
- **A known ID is missing despite an ID-only summary:** clear partial Data selections and conflicting/reversed dates, confirm the selected property, and Search again. If the row is still missing, escalate with the ID rather than changing inventory.
- **The request disappears after retry/archive:** its status or archive flag may no longer match your search. Search by ID or use All status and Include Archived Updates. Disappearance alone is not proof of delivery.
- **Go reports no action or no requests selected:** select the intended action and tick the intended rows. If **Actions do not match** appears, make the top and bottom dropdowns agree before continuing.
- **Some selected requests are left out:** they are no longer valid requests of the current property. Reload and reselect the intended rows. Ask support if the scope remains unclear; do not switch property context to bypass the warning.
- **An action is denied:** ask your administrator to check update permissions. Public demo accounts are restricted to searching here.
- **A request stays Pending/Processing, fails again, or reappears after archiving:** Search again and inspect its message and timestamps. Archive does not stop processing or automatic retry. Contact support with the request ID before repeated manual retries.

## Related

- [Inspect an inventory update request log](https://help.channelrush.com/hc/channelrush/articles/update-request-log)
- [Understand your inventory processing summary](https://help.channelrush.com/hc/channelrush/articles/updates-status-summary)
- [Update rates, availability and restrictions with Quick Update](https://help.channelrush.com/hc/channelrush/articles/quick-updates)
