Open the diagnostic log for an inventory update, read its recorded attempts, and download the available evidence for support without resending inventory.
Before you start
- You need to be signed in and have access to the affected property.
- Start with an existing inventory update request. This guide concerns rates, availability and restrictions sent to channels, not reservation delivery.
- Viewing a log and downloading it do not require permission to change inventory. A Logs link is available only for eligible requests; not every request has stored log entries.
Opening Logs or saving its file does not retry the request, change inventory or resolve an error. Do not use Retry or Go to open a log.
Find the request
- Select the affected property in the property selector.
- Open Updates → Status.
- Choose the relevant Status, Channel, Room Type or Rate Plan filters. Leave Status at All if you are unsure of the current processing result.
- Click Search.
- Find the request with the expected channel, products, inventory dates and values.
- Note its ID, Status, Attempts, Created and Last Run information.
- Click Logs beside that request.
If the request is not on the current results page, use » to see the next page and « to return, when those controls are available. You can also narrow the filters and click Search again.
The log opens in a new tab, leaving Update Status available for comparison. You do not need to tick the request's checkbox. Search loads matching requests; Go runs the selected action and is not part of this viewing workflow.
Find a known request ID
- Open More Filters on Update Status.
- Enter the request's ID in Transaction ID.
- Clear any selected Rates, Availability and Restrictions checkboxes under Include Data Types to avoid excluding the request by its recorded data types.
- Click Search.
- Confirm the returned request's ID and property before opening Logs.
Transaction ID is the inventory request identifier, not a reservation number. After date validation, an exact-ID search takes precedence over the ordinary channel, status, product, user, source, archive and date filters, but a partial data-type selection can still exclude it. The search remains within the selected property.
If you see The End Date cannot be before the Start Date., clear both dates or correct their order, then click Search again. An invalid date order prevents the search even when you supply a Transaction ID.
If you search without an ID, Archived includes archived requests alongside other matching requests. The date choice also matters: Start/End Date concerns the affected inventory dates, while Creation Timestamp and Processing Timestamp concern the request's recorded activity. These are different from the individual message timestamps inside the log.
Check that you opened the correct log
At the top of Update Request Log View, check:
- The channel name.
- The request ID.
- The property name beneath it.
If any of these is wrong, return to the Update Status tab and open the correct request. Do not alter identifiers in the address bar to try to reach another property or request.
The viewer has no inventory editor, retry button or search form. Use the original Update Status tab when you need to search again. Close the log tab when you have finished.
Read the recorded attempts
When entries are available, the page displays text grouped under ATTEMPT #… headings. Each entry can contain a REQUEST or RESPONSE label, a timestamp, a URL and the recorded message. XML and JSON messages are formatted for reading; other messages appear as text.
Read the message itself as well as its label. RESPONSE means an entry is presented as a response; it does not mean the channel accepted the update. A response can contain an error or warning. An attempt number is not a count of successful deliveries, and a visible request entry alone does not establish that a response was received.
Log-message timestamps use UTC, including milliseconds and a UTC offset. Update Status's Created and Last Run values use your user time zone. Account for that difference when comparing events or telling support when something happened. Inventory dates inside a message describe the dates being updated, not necessarily the time the message was sent.
Log field reference
| Item | What it means and how to use it |
|---|---|
| Channel | The channel associated with the selected request. Check it against the request you were investigating. |
| ID | The inventory request ID. Quote it with the property and channel when asking support to investigate. |
| Property | The property whose log you opened. It appears beneath the channel and ID. |
| ATTEMPT #… | The stored attempt associated with the following entries. Multiple entries can belong to one attempt. A missing or unexpected number is a reason to ask support, not to assume success or trigger another send. |
| REQUEST / RESPONSE | The entry's diagnostic label. Use the accompanying message to understand what was recorded; the label is not a processing result. |
| Timestamp | The recorded message time, shown in UTC with milliseconds. It is separate from affected stay dates and the user-time-zone timestamps on Update Status. |
| URL, when present | The recorded endpoint for the entry. It is diagnostic context, not a link you need to open or replay. Review URLs for sensitive information before sharing them. |
| Message | The recorded XML, JSON or other text. Look for the relevant dates, products and any error or warning. Do not assume that every channel uses the same response format or success indicator. |
| Save Log File | Downloads the currently available entries for this property, channel and request as a text file. It does not send the file to support or resend inventory. |
Download the log
- Confirm the property, channel and request ID in the log header.
- Click Save Log File.
- Open the downloaded text file and check that it contains the evidence you expected.
- Review the entire file, including URLs, before sharing it through your approved support channel.
When entries are available, the filename follows UpdateRequest-{ID}-Log.txt. When no entries are found, it follows UpdateRequest-{ID}-E.txt and contains no log entries. The E filename is not a verdict that the inventory update failed.
The download reads the available log again. It is not a screenshot or an exact copy of the page's formatting; labels and spacing can differ. If entries become available between opening the page and downloading, the file can differ from the earlier view.
Treat logs as potentially sensitive. Do not assume that every credential or personal detail has been removed. Never post logs publicly or send passwords, API keys, payment details or unnecessary guest information. If you are unsure how to share the evidence safely, provide the property, channel and request ID first and ask support for the appropriate next step.
Check the result
You have collected diagnostic evidence when the log header matches the intended request and you have reviewed the available entries or downloaded file. That is separate from resolving the update problem.
Return to Updates → Status, verify the property and search criteria, and click Search again to check the stored processing result and any status message. Successful is the request's processing result, not a fresh check of the channel's current inventory. The log viewer itself does not provide a separate acceptance confirmation or verify current rates and availability.
If the result or response is unclear, give support the property, channel, request ID, affected inventory dates, relevant product, error text and the action time with its time zone. Include any retry already performed. Ask for the correct recovery action before resending inventory.
Common problems
Logs is missing
The link is not shown while a request is Pending or Processing, or before it has a processing attempt. Older request records can also lack this link. Search again to check the current result; do not retry merely to make Logs appear.
If the request remains in an unexpected state or you need evidence that is unavailable, contact support with its ID, property and channel. A missing link does not establish that nothing was sent.
Logs opens, but the body is blank
The viewer can show the correct channel, ID and property with an empty body when no log entries are available. The presence of Logs on Update Status does not guarantee stored content.
Check the identifiers, return to Update Status and click Search to review the request's result. If the evidence is still needed, contact support. Do not treat a blank log or empty download as proof of either success or failure, and do not generate a new update to obtain a log.
The expected request is not in the search results
Confirm the property and request ID. For a known ID, use Transaction ID, clear partial data-type filtering, and click Search. Without an ID, check the status, product, date and Archived filters.
If the request is still unavailable, provide support with the known identifiers and approximate action time. An empty search does not prove that the original update was never saved or sent.
The log time differs from Update Status
The message log uses UTC; Update Status uses your user time zone. Compare the time zones before reporting an ordering or timing problem. If the events still do not line up, include both timestamps and their zones when escalating.
A response contains an error, or the result is unclear
Record the error text and relevant attempt and timestamp. Compare it with the request's status message. Do not assume that a response label, an HTTP success indication in the text, or a later attempt means the entire update was accepted. Ask support to interpret an unfamiliar channel response before choosing a recovery action.
The download is empty or does not open as expected
Check whether the filename ends in -E.txt and whether the viewer is also blank. An empty file supplies no diagnostic entries. If a file with expected content cannot be read, report its filename, property, channel, request ID and browser to support; do not modify inventory to troubleshoot a download.
Related
- Send inventory update requests to support — the separate workflow for submitting selected request summaries and an explanation.
- Investigate inventory update requests across properties — the organization-wide workflow for users with the relevant access.