Find the inventory update requests behind a rate, availability or restriction change, understand their processing results, and decide whether to contact support, retry or archive them.

## Before you start

- Open **Org Admin → Updates**. The heading is **Update Requests - Processing Status**. The Org Admin menu is available to organization administrators and users with access to multiple properties; available properties remain limited by your account access.
- This page is for outbound inventory updates, not reservation delivery. **Go To Report Status** switches to inventory-report requests; it is not the result of sending an update.
- Choose the **Property** inside **Search Filters**. The property selected in the application's top bar is not a substitute for this search filter. **All** searches your accessible scope, not only the top-bar property.
- Searching does not resend inventory. **Go** runs the selected action. Retry and archive operations require at least one of the update permissions for rates, availability or restrictions. The public demo login can search, but cannot run these actions or submit a support request from this page.

## Find the requests

1. Open **Org Admin → Updates**.
2. Select the affected **Property** in **Search Filters**.
3. Select the destination **Channel**, if known.
4. Select **Status**, or leave **All** to avoid hiding a request whose status has changed.
5. Click **Search**.
6. Open **More Filters** if you need to narrow by product, source or dates.
7. Choose the additional filters described below.
8. Click **Search** again.

Selecting a filter does not load new results by itself. Check the retained selections and the displayed requests after every search. Choosing a property and searching first also supplies that property's **Room Type** and **Rate Plan** choices.

![Primary search filters showing a demo property, Successful status and ChannelRUSH Booking Engine](https://support.channelrush.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBcHdCIiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--fe22ff8a3d7f7c0a59fa2bfcd01830f931a4f441/status-updates-filters.png)

*The search controls are stacked at narrower screen widths. These are the same filters as on the desktop layout.*

The initial page can show an empty table before a search. **Clear Search Filter** clears the search criteria; it does not clear saved requests. Use **Search** to load the scope you want. The **«** and **»** paging links move through results, normally 50 requests at a time, with the newest request IDs first.

### Find a known request ID

1. Select the correct **Property**.
2. Open **More Filters**.
3. Enter the request's numeric **ID** in **Transaction ID**.
4. Leave all three data-type switches—**Rates**, **Availability** and **Restrictions**—off, or turn all three on.
5. Click **Search**.

This is the inventory request ID, not a reservation number. An exact-ID search still respects your accessible property scope, but bypasses most other filters, including status, channel, dates, source and the usual archived exclusion. A partial data-type selection can still hide it. The page may update Status and clear the dates after finding one request; do not interpret that as a change to the request itself.

## Read a request and check the result

Each request shows its property, channel, room type and, when applicable, rate plan. The **Updates** column shows the affected inventory dates, selected weekdays and the values carried by the request. These dates are different from when the request was created or processed.

![A complete demo inventory request with allocation, Successful status, attempt count, request ID and timestamps](https://support.channelrush.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBcDRCIiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--29dc82a8fd8b52983712f8cc7900c2a3844bf161/status-updates-request.png)

*This example is a stored allocation update. Its successful processing status is not a fresh comparison against inventory currently displayed by a channel.*

Look beneath the values for:

- **Status:** the current processing result. Read any accompanying error or explanation, not only the colored marker.
- **Attempts:** the processing attempt count. It is not a count of confirmed successful network deliveries.
- **Source and user:** where the request originated. For example, the filter label **UI Quick** appears as **UI - Quick** in a result. A PMS-related source can show its channel name instead of an individual user.
- **Archived:** when present, the request has been marked archived. This is separate from its processing status.
- **ID:** the request's internal identifier, useful for Transaction ID searches and support.
- **Created:** when the request was created.
- **Last Run:** the request's recorded processing/edit time. Queuing a retry also changes this value, so a new Last Run time alone does not establish a completed send. The displayed timestamps use your user's time zone; retain the zone when reporting a problem.
- **Logs:** opens the available attempt log in a new tab. Logs use **UTC**, unlike the localized timestamps on this list. **Save Log File** downloads the available log text; it does not resend the request. A missing or empty log is not proof of success or failure.

### Status meanings

| Status filter | What it establishes |
|---|---|
| **All** | No status restriction. Use this when following a request through status changes. |
| **Pending** | Waiting for processing. It does not establish channel acceptance. |
| **Processing** | Processing is in progress. Investigate before starting a duplicate retry. |
| **Successful** | ChannelRUSH recorded successful processing. This is not a guarantee that every current channel value matches the intended inventory. |
| **Unsuccessful** | Processing did not succeed. Read the message and resolve the relevant issue before considering another attempt. |
| **Failed** | A failed processing result requiring investigation. It can include communication or other processing errors; the label alone does not identify the cause. |

**Important:** a request selected by the **Failed** filter can display **Status: Unsuccessful** in its row. Use the filter and message together; **Unsuccessful** and **Failed** are separate search statuses.

For an update you are following, note its ID, search again with **All** or by **Transaction ID**, and inspect the latest status, message and logs. A request disappearing from an unsuccessful-only search can mean its status changed. An empty search does not establish delivery, and a processing result is not a substitute for checking the intended dates and values in the channel when that confirmation is required.

### Counts above the results

Some searches show **Pending**, **Unsuccessful** and **Failed** panels. Each panel counts that status within the other applicable filters, excluding archived requests. These are not a total of all statuses or a count of the rows currently displayed.

Counts above the reporting bound show **10,000+**. The number followed by **p** is the corresponding page count; it can also be capped. Exact-ID searches can make these status panels misleading because the ID takes precedence over the status filter. Use the matched request itself in that case. These display caps do **not** limit the scope of an **All** action.

## Additional filters and field reference

![Expanded filters for organization, request ID, room, rate plan, source, dates and data types](https://support.channelrush.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBcDBCIiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--1bb3ac91d65270d96d6bfdd52f3a3b2025502dd3/status-updates-more-filters.png)

### Property, channel and origin

| Field | What it does and how to use it |
|---|---|
| **Property** | Limits results to one accessible property. **All** uses your accessible organization/property scope. Set this explicitly for a property-specific investigation. |
| **Status** | Matches one processing status, or **All**. See the status reference above. |
| **Channel** | Limits results to one destination channel. This is different from **Source**, which describes the origin of the update. |
| **Users** | Intended to select the user associated with a request. The selection is currently not retained by the normal Search/paging route. Do not rely on it to isolate work or define an action's scope; use property, channel, source and known request IDs instead. |
| **Organization** | Appears when multiple organizations are available. Changing it clears the Property selection. Reselect the intended property and click **Search**. Only use organizations you are authorized to access. |
| **Transaction ID** | Finds one internal inventory request ID, subject to accessible scope. Overrides most other filters; see the known-ID procedure above. Clear it before returning to an ordinary search. |
| **Room Type** | Limits results to the selected property's standard room type. Search with Property selected first if choices are missing. |
| **Rate Plan** | Limits results to the selected property's standard rate plan. This is not a text search for an OTA rate code. |
| **Source** | Matches the origin of the request. **All** leaves it unrestricted. Choose the workflow that generated the update rather than the destination channel. |

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

### Date Range

Choose the meaning of the dates before entering them:

- **Start/End Date:** filters the dates the inventory update affects. With both dates entered, requests whose inventory-date span overlaps your range can match, including requests that start earlier or finish later. Start alone means the request starts on or after that date; end alone means it ends on or before that date. Date-span matching does not independently test the request's selected weekdays.
- **Creation Timestamp:** filters when the request was created, not the stay dates it updates.
- **Processing Timestamp:** filters the recorded processing/edit timestamp used for **Last Run**. A retry can change it before a completed send.

Leave both dates blank for no date restriction. Use the date controls' displayed local format. If you see **The End Date cannot be before the Start Date.**, correct the range and search again; do not rely on results shown alongside that error.

**Timestamp searches have different end-date behavior from inventory-date searches.** A multi-day timestamp range does not cover the whole final day. If you are looking for an event late on that date, widen the range beyond it and check the timestamps on the returned rows. A start-only timestamp search avoids an end-date cutoff; an end-only search ends at the entered date boundary. Entering the same start and end date uses a one-day window. For precise event identification, use the request ID and include the displayed time zone when contacting support.

### Archived and Include Data Types

| Switch | Meaning |
|---|---|
| **Archived** | Includes archived **and** nonarchived requests. Off normally excludes archived requests; an exact Transaction ID search can still find them. This is a visibility filter, not an action. |
| **Rates** | Matches requests with recorded rate changes, including net/sell rates and additional rate parameters. |
| **Availability** | Matches recorded allocation **or Stop Sell** changes. Stop Sell belongs to this filter, not Restrictions. |
| **Restrictions** | Matches recorded arrival/departure closures, minimum/maximum nights, through-night restrictions or cutoff-day changes. |

With none or all three of **Rates**, **Availability** and **Restrictions** selected, there is no data-type restriction. Selecting one or two finds requests containing any selected type; it does not require every selected type. The whole matching request is shown, including its other values. Older requests without recorded change-type details can disappear under a partial selection.

**Check Archived again after searching or paging.** In searches that calculate the status counts, the switch can return to off even when archived results were loaded. Do not use the displayed switch alone as proof of the loaded scope. If the selection and results disagree, avoid an **All** action; locate the known ID or contact support.

### Values within Updates

The fields shown depend on what the request contains and what its channel supports:

- **Sell Rate / Net Rate:** amounts and currency. An asterisk identifies the request's selected rate type.
- **Allocation:** the available-room quantity carried by the request.
- **Stop Sell:** whether the request closes or opens sales for its scope.
- **CTA / CTD:** closed to arrival / closed to departure.
- **Cut Off Days:** the advance-booking cutoff value.
- **Min Nights / Max Nights:** the minimum/maximum stay values.
- **Min Nights Through / Max Nights Through:** the through-stay restriction values.
- **Additional rate or channel parameters:** channel-specific values, shown when present.

A missing field is not automatically zero, No or a removal instruction. This screen displays stored request details; it is not an editor. **VRT** identifies a virtual room type. **[BLANK / NOT SET]** indicates missing product-name information and warrants checking the setup before deciding to retry.

## Send the evidence to support

Use this when the message or delivery outcome is unclear. Sending evidence is separate from retrying inventory.

1. Find the affected requests with **Search**.
2. Tick the checkboxes beside the specific requests.
3. Choose **Send to SLS** in the action dropdown.
4. Click **Go** to open **Send To Support**.
5. Review the selected requests and **Subject**.
6. In **Message**, explain the symptom, expected result, affected dates and action time with its time zone. Include the request IDs and relevant error text.
7. Click **Send** when you intend to send the request to support, or **Cancel** to leave without sending.

Opening the support form does not send it. **Send** submits your message with generated request details. Those details are not a complete raw payload or an automatic attachment of every attempt log; describe the issue in your own message. The confirmation records the support-send action, not that the inventory problem has been resolved. No receipt time or resolution time is promised here. Never include passwords, payment details or unnecessary guest data.

Recheck your filters when returning from the support form: not every selection is preserved. If the send result is unclear, check with support before repeatedly sending the same request.

## Retry, archive and unarchive safely

These actions change requests. Do not use them to refresh the screen, and do not assume a second confirmation dialog will appear after **Go**.

The checkbox in the table heading selects only the requests on the current page. **Retry**, **Archive** and **Unarchive** use the individually selected requests. **Retry All**, **Archive All** and **Unarchive All** use the matching search scope, including records on other pages—not the checked rows and not only the displayed count.

Before an **All** action, choose the final filters and click **Search**. Verify the scope, clear any unintended Transaction ID, and do not change filters between that search and **Go**. If a filter is not retained correctly, use specific request IDs or escalate instead.

### Retry

**Retry can also requeue later overlapping requests for the same property, channel and mapped products.** Those additional requests need not share the selected status or source. Retrying is not a harmless replay of only the highlighted row; processing can use current settings. Ask support to confirm the intended scope if you are unsure.

1. Read the message and resolve the underlying issue, or obtain support's recommendation to retry.
2. Search again and check that the request is not already Processing and the intended inventory dates are still relevant.
3. Tick the specific requests you intend to retry.
4. Select **Retry**.
5. Click **Go**.
6. Search again using the known IDs or **All** status, and inspect the resulting status, message and logs.

**Retry All** requires a specific **Property**, **Channel** and **Status**, even if a validation message suggests fewer filters. It can select matches beyond the current page and can expand to later overlapping requests as described above.

Requests selected for retry become Pending, are unarchived, and have their prior message cleared. The attempt count is not reset. Past-only inventory requests may no longer be eligible. A success banner means the retry action was accepted, not that every selected request changed or that the channel accepted the inventory. Do not repeat Retry merely because delivery is not yet confirmed.

### Archive and unarchive

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

1. Search for the requests and review their status and dates.
2. Tick the intended rows.
3. Select **Archive** or **Unarchive**.
4. Click **Go**.
5. Locate the known request IDs or search with **Archived** enabled, then check the archive indicator.

Unarchive only removes the archive flag; it does not itself request a retry. **Archive All** and **Unarchive All** require one **Property** and one **Channel**. To include archived records in an ordinary search, enable **Archived** first, but heed the filter-retention warning above before any all-matching action. Neither action changes the processing status or proves a delivery problem has been fixed.

## Common problems

- **No requests appear:** the initial screen may not have loaded a search, or status/product/source/date/archive/data-type filters may exclude the request. Click **Search**, broaden the relevant filters, or use a known Transaction ID with all data types included. If still missing, send support the property, channel, dates and action time; do not resend inventory solely because the list is empty.
- **A Failed result says Unsuccessful in its row:** the row combines these labels. Keep the exact **Failed** filter and read the message. Contact support when the cause is unclear rather than assuming it is a configuration error you can fix by retrying.
- **Users or Archived does not stay selected:** these controls have the limitations described above. Recheck the returned scope. Do not run an All action on a scope you cannot verify.
- **Retry All is refused:** select a single Property, Channel and Status, then Search again. Archive All and Unarchive All need Property and Channel. Do not broaden scope to work around a validation message.
- **Go reports no action or no requests selected:** choose the intended action and, for a selected-row action, tick the requests. If top and bottom action choices disagree, make them match before proceeding.
- **Some selected requests are excluded:** your access does not cover those properties. Ask an authorized administrator to investigate; do not try another property context to bypass the restriction.
- **An action is unavailable or denied:** check update permissions with your administrator. Public demo accounts are limited to searching here.
- **A request stays Pending/Processing, fails again, or returns after archiving:** refresh the investigation with Search and inspect its message and logs. Archiving does not stop processing or automatic retry. Contact support with the ID and observed timestamps before repeated manual retries.

## Related

- [Check inventory update status across properties](https://help.channelrush.com/hc/channelrush/articles/inventory-status-per-hotel)
- [Review inventory consistency across channels](https://help.channelrush.com/hc/channelrush/articles/inventory-consistency)
- [Update rates, availability and restrictions with Quick Update](https://help.channelrush.com/hc/channelrush/articles/quick-updates)
