Use **Report Requests - Processing Status** to find an inventory-report request, understand its current processing state, and decide whether to investigate, retry or archive it.

These requests retrieve inventory information. They are **not outbound rate or availability updates, reservation deliveries, or scheduled email reports**. **Search** reloads stored request information. **Go** performs the chosen action; it is not another search button.

## Before you start

- Sign in to the correct organization with access to the properties you need. The **Org Admin** navigation path below requires organization-administrator access. A directly shared request-status link still checks your authorized property scope.
- The property in the application header is navigation context. Use **Property** in **Search Filters** to restrict this list to one property; do not assume the header selection does that for you.
- Retry, archive and unarchive require permission to update at least one of rates, availability or restrictions. Ask your administrator if an action is refused. Public demonstration sessions can search but cannot perform these actions or submit support email.

## Find the requests

1. Open **Org Admin → Home**.
2. In the **Channel Manager** section, select **Report Status**. Check that the page title is **Report Requests - Processing Status**.
3. Choose **Organization**, if offered, and then **Property**. Leave unrelated filters at **All** for the first search.
4. Select **Search**. Choosing a property and searching loads that property's **Room Type**, **Rate Plan** and **Channel** choices.
5. Narrow the search using **Status**, **Channel**, the product fields, **Requested By**, or the date filters described below.
6. Select **Search** again to apply your changes.

![Inventory-report request Search Filters for a demo property, showing Failed, Booking.com, product filters, archive inclusion, stay dates and request timestamps](https://support.channelrush.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBdFVCIiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--45864594cbb6196f9638650eb2217397645430e9/status-reports-filters.png)

*The filter form in a narrower browser window. The example searches one demo property; it does not show a failed request or a completed retry.*

Review the applied **Filtered by** labels and the request rows before acting. Changing **Organization** clears the Property selection; changing **Property** clears Room Type and Rate Plan. Search again before selecting dependent product filters. **Clear Search Filter** removes the explicit search criteria; check the resulting scope and select Search when you are ready. It does not clear or delete requests.

**Go To Update Status** opens the separate outbound-update screen. It does not carry this search across unchanged and does not show the result of a report retry.

### Find one known request

Enter its numeric **Request ID**, choose the correct Property, and select **Search**. Request ID takes precedence over the ordinary status, channel, product, user, archive and date filters, but it does not bypass property access. You can use it to find an archived request without relying on the archive checkbox. Correct any date-order errors before taking an action, even when searching by ID.

## Understand the results

Requests are listed newest ID first, normally 50 at a time. Use the previous/next arrows for other pages. The header checkbox selects **only the requests on the displayed page**, not all matching requests. A next-page arrow can lead to an empty page at the end; return to the previous page rather than treating that as a new processing outcome.

The table's **Hotel / Channel** column identifies the property, channel and available room/rate-plan details. Channel and product links open channel settings. **VRT** identifies a virtual room-type mapping. **Dates** is the inventory date range requested, not when the request was created or processed.

Each request also provides:

| Detail | How to read it |
|---|---|
| **Status** | The processing state described below. Read the message beneath the request as well. |
| **Attempts** | Recorded processing attempts. Clicking Retry does not immediately increment this number. |
| User name and ID, or **API** | The recorded requesting user. API appears when no user is recorded; it does not identify a particular external application. |
| **ARCHIVED** | Hidden from ordinary searches unless included explicitly. Archiving does not resolve the underlying issue. |
| **ID** | The request identifier to keep for investigation and support. A retry reuses this ID. |
| **Created** | When the request record was created. |
| **Last Run** | The request's recorded last-update time. It can already be populated on a Pending request with zero attempts, and is not necessarily a channel-response or completion time. |
| Message beneath the request | Recorded processing information or an error. Preserve it before retrying because later processing can replace it. |

Created and Last Run use your signed-in timezone, also shown beside the date filters. A blank product name or **[BLANK / NOT SET]** is a reason to inspect the mapping, not proof of the request's processing outcome. This page has no request-delete or export action.

### Processing states

| Status | Meaning and safe next step |
|---|---|
| **Pending** | Waiting for processing. Search again to check progress; do not repeatedly retry it. |
| **Processing** | Work is in progress. A processing timestamp is not completion. Preserve the request ID and contact support if progress cannot be established. |
| **Successful** | The request was recorded as processed successfully. This alone does not prove a fresh live channel read, matching inventory values, or that every retrieved inventory image was saved. Check the relevant inventory report when investigating values. |
| **Unsuccessful** | The operation did not complete as required. Read the message and review the named setup, mapping or date issue with an authorized administrator before retrying. |
| **Failed** | Processing recorded a failure. Preserve the message and request details for investigation; the label alone does not establish who can fix it or whether nothing happened. |

**Unsuccessful and Failed are separate selections on this page.** Search each when investigating both kinds of problem.

### Pending, Unsuccessful and Failed counters

Some filtered searches show these three counters above the list. They count each status separately, exclude archived requests, and retain the other applicable search restrictions. They are not totals for the currently displayed page or a breakdown of every status. They may appear after choosing Channel and Status even when no requests match.

The number in parentheses ending in **p** represents pages at the current page size, not a percentage or estimated processing time. Large counts are capped and displayed with **+**. For an exact Request ID search, rely on the row's Status rather than these counters: the ID overrides their status restrictions. Correct date errors before interpreting any counts.

## Retry only after investigating

A retry is real processing, not a refresh. It can retrieve inventory and update stored report images. It is not an outbound rate update, and it does not guarantee that the original historical date span will be processed unchanged.

1. Record the request ID, property, channel, Dates, Status, Attempts, Last Run and message.
2. Resolve the cause with an authorized administrator or support, and confirm the request is still needed. Do not retry requests already Pending or Processing.
3. Apply the intended filters with **Search** and select the intended request checkboxes.
4. Choose **Retry** in the action selector.
5. Select the adjacent **Go**.
6. Search for the same **Request ID** to follow its progress.

The confirmation means the selected requests were **marked for retry**, not completed. Retry sets them to Pending and removes their archived flag. Their old message, attempt count and Last Run can remain visible until processing updates the record. A Failed or Unsuccessful filter can hide a request as soon as it becomes Pending or Successful; disappearance from that list is not a success check.

Use **Retry All** only when you intend to affect every matching request, including other pages. Select a specific **Property**, **Channel** and **Status**, apply **Search**, review the scope, then choose Retry All and Go. All three selections are required, even if an error message suggests Property or Status is optional. Changes to filters after Search can change the scope used by an All action. Do not use it when the scope is unclear.

## Archive and unarchive

Archiving is shared request housekeeping, not a personal dismissal. It hides requests from ordinary searches; it does **not** delete them, fix their errors, or cancel Pending/Processing work. Work already eligible for processing may continue and become visible again.

To archive reviewed requests, apply **Search**, select their checkboxes, choose **Archive**, and select **Go**. Confirm the banner, then search an individual Request ID if you need to check its ARCHIVED marker. Do not interpret an empty ordinary search as successful processing.

To restore a known archived request, search its **Request ID** within the correct property, select it, choose **Unarchive**, and select **Go**. This restores ordinary visibility. It is not an immediate manual retry, but it can make a recent failed request eligible for automatic retry again. Confirm that renewed processing is wanted before unarchiving.

**Include Archived Reports** is a viewing option: it includes archived and unarchived requests, not archived requests alone. It does not unarchive anything. There is a current limitation: after some searches the checkbox clears and the applied-filter labels omit it. Check it again before another archive-inclusive Search, and do not assume paging retains it. Use a known Request ID for reliable individual investigation; contact support if you need a complete archived list.

**Archive All** and **Unarchive All** target all matching requests, not the checked rows. They require a single property and channel, but the current screen can still reject them after those selections. Use selected-row Archive or Unarchive instead of broadening the scope or repeatedly submitting an All action. Escalate the contradictory validation if a bulk operation is necessary.

## Send requests to support

**Send to SLS** means send to second-level support. It starts a support-message workflow; selecting it does not retry the requests.

1. Search for and select the intended requests.
2. Choose **Send to SLS** and select **Go** to open the message form. This step does not send the email.
3. Review **Subject** and enter a useful **Message**: the problem, expected result, affected property/channel/dates, and relevant action time and timezone.
4. Review the included request list.
5. Select **Send** to submit the support email, or **Cancel** to return without sending.

Request details are included in the message. Do not add passwords, payment details or unnecessary guest information. The confirmation reports submission to support; it does not establish that someone has read it or that the report failure is resolved. If the page reports an error or the outcome is uncertain, check with support before submitting duplicates.

## Filter reference

| Field | What it changes |
|---|---|
| **Property** | Narrows the search to one authorized property. All means no single-property narrowing within your accessible scope; it is not the property selected in the application header. |
| **Organization** | Offered when more than one organization choice is available. Narrows organization scope; changing it clears Property. |
| **Status** | All, Pending, Processing, Successful, Unsuccessful or Failed. Unsuccessful does not also include Failed here. |
| **Channel** | Narrows to one listed channel. Its presence in this dropdown does not prove it supports a live inventory read. |
| **Room Type** | Select a Property and Search to load its standard rooms. All leaves the room unrestricted; a specific room matches requests recorded against that room, not requests with no room specified. |
| **Rate Plan** | Select a Property and Search to load its standard rate plans. A specific choice matches that standard plan. The row may display its channel-mapping rate-plan name. |
| **Requested By** | Filters by the recorded requesting user. All applies no user restriction. Available users depend on your scope. |
| **Request ID** | Exact numeric request identifier. Overrides ordinary search filters, including archive exclusion, while retaining authorized property scope. Leave blank for a list search. |
| **Include Archived Reports** | Off by default. When checked, includes archived as well as unarchived requests. See the retention limitation above before paging or taking actions. |
| **Stay Dates** | Filters the inventory dates requested. Either endpoint may be blank. Two dates match requests overlapping that period, not only requests entirely inside it. For example, a request spanning the whole month can match a two-day search. |
| **Date and Time: Created / Last Run** | Chooses which request timestamp to filter. Created is the initial choice; no timestamp restriction applies until a date is set. Last Run uses the recorded last-update time, not a guaranteed completion time. |
| **Date and Time dates and optional times** | Uses your signed-in timezone. Start without a time begins at the start of that local day; end without a time includes the entire final local day. A specified end time includes that whole minute. Either endpoint may be blank. A time without its date has no effect. |

Both date ranges are optional and distinct. Stay Dates answers “which inventory dates?”; Date and Time answers “when was the request created or last updated?” There is no Source or Rates/Availability/Restrictions filter on this screen.

## Common problems and result checks

- **No rows appear.** Check Property, Request ID, Status, archive inclusion and both date ranges. Search Unsuccessful and Failed separately. Remove unnecessary product/user restrictions and Search again. An empty list is not proof of successful processing or that no earlier request existed. If a known ID remains absent in the correct scope, give it to support.
- **Room Type or Rate Plan contains only All.** Select the intended Property and Search first. If expected products are still missing, ask your administrator to check the property setup rather than guessing a mapping.
- **“The End Date cannot be before the Start Date” or “The last stay date cannot be before the first.”** Correct the corresponding range and select Search again. Rows can still appear with a date error; do not act on that result or rely on its counters.
- **An action reports no action or no requests selected.** Choose the intended action and, for selected-row actions, tick the requests first. Use Search to refresh uncertain scope, not Go. If the top and bottom selectors disagree, make them consistent before submission.
- **Some selected requests were left out.** They could not be resolved within your current authorized property scope. Re-search and confirm access with your administrator; do not substitute a broader selection.
- **A retry is confirmed but the old error remains.** Confirmation is not completion. Search the same ID and review subsequent Status, Attempts, Last Run and message. Avoid repeated retries while it is Pending or Processing; escalate if progress cannot be established.
- **Archive inclusion clears or a bulk archive is refused despite selecting a property and channel.** Use the individual-ID and selected-row procedures above. If those do not establish the needed scope, stop and contact support with the filters and error text.

For escalation, include the request ID, property, channel, requested inventory dates, selected filters, relevant times/timezone and exact error text. Distinguish what you searched from any action you actually submitted.

## Related

- [Check inventory-report request status across properties](https://help.channelrush.com/hc/channelrush/articles/report-status-per-property)
- [Investigate inventory update requests across properties](https://help.channelrush.com/hc/channelrush/articles/status-updates)
- [Choose filters for a rates and availability report](https://help.channelrush.com/hc/channelrush/articles/channels-report-filters)
