Search
Clear search
Close search
Google apps
Main menu

Feed error codes

Error typeError codeExplanationError Messaging How to fix
Transaction1001The timestamp format is very specific. It requires the timezone offset or Z, and it does not accept fractional seconds.Timestamp "%s" not in format "YYYY-MM-DDTHH:MM:SS<+|->HH:MM" or "YYYY-MM-DDTHH:MM:SSZ"Correct the format.
Transaction1002The currency code was not a valid one. See the Help Center document for allowed currency codes.Invalid currency code in converting Taxes from %s to %sUse a valid currency code.
Transaction1003The currency code was not a valid one. See the Help Center document for allowed currency codes.Invalid currency code in converting OtherFees from %s to %sUse a valid currency code.
Transaction1004This indicates an internal error during processing.Internal error: Invalid availability result for partner %s, %sPlease contact your TAM.
Transaction1005This occurs from any of: invalid baserate currency, no Baserate, invalid Taxes currency, invalid OtherFees currency.Invalid taxes and fees for partner: %s, %sEnsure valid currency codes, and a baserate exists for all prices.
Transaction1006The "all inclusive" flag indicates that taxes and fees could not be separated from the baserate, but this itinerary also contained a value for taxes.All inclusive specified, but taxes provided for partner: %s, %sIf taxes are known, correctly separate baserate from taxes and do not report all_inclusive.
Transaction1007This indicates a Result tag was seen somewhere unexpected.Result is expected only as immediate child of Transaction, but found elsewhereEnsure Result is only given as a child of Transaction.
Transaction1008This indicates a RoomID tag was seen in an inappropriate context.RoomID outside of RoomData/RoomBundle contextEnsure RoomID is only used where indicated.
Transaction1009This indicates a PackageID tag was seen in an inappropriate context.PackageID outside of PackageData/RoomBundle contextEnsure PackageID is only used where indicated
Transaction1010This indicates a RatePlanID was seen in an inappropriate context. RatePlanID is only valid in a RoomBundle.Use of RatePlanID within RoomData/PackageData is not storedDo not use RatePlanID outside of allowed contexts
Transaction1011This indicates a Capacity or Occupancy was seen in an inappropriate context.Capacity/Occupancy outside of a RoomBundle/RoomData/PackageData not storedOccupancy/Capacity are only appropriate in a RoomBundle, RoomData or PackageData
Transaction1012To prevent likely data errors, Google limits the maximum capacity or occupancy to 20.Will not use Capacity/Occupancy of %d, which is over Google limit of %dDo not send capacity or occupancy information that exceeds 20
Transaction1013The text value for occupancy or capacity could not be parsed as an integer.Unable to interpret %s as a number for occupancy/capacityCorrect the format
Transaction1014Unparseable boolean provided. Accepted values are: 0, 1, true, false.Unable to interpret %s as a booleanCorrect the format
Transaction1015Text was provided for an element that does not accept text.XML text \"%s\" provided in XML element %s not in schemaRemove the text
Transaction1016The Text element (as opposed to text value) was used in an inappropriate context.Use of Text outside of an appropriate context ignoredFind the correct context and relocate or remove the Text
Transaction1017The Refundable element was used in an inappropriate context. It is usable in RoomBundle, RoomData and PackageData. It is not allowed directly in Result.Use of Refundable outside of an appropriate context ignoredFind the correct context and relocate or remove the Refundable
Transaction1018Google sets a limit on maximum refundable days, mostly to avoid incorrect data.Will not use %d refund days, which is greater than Google limit %dCorrect the value, if possible. If the actual value is above the limit, code this room as non-refundable
Transaction1019Unparseable number provided.Unable to understand %s as a number for refundable daysFix the formatting
Transaction1020Unparseable time provided.Unable to understand %s as HH:MMFix the formatting
Transaction1021The named element does not accept attributes.XML Element %s has no attribute named %s to give value %sRemove attributes for this element
Transaction1022Google does not have a mapping from this partner ID to a Google ID. This could be due to delays in Google's processing or if we were unable to match the partner ID. See documentation on the hotel feed.Unable to find a Google Hotel ID for partner %s, partner hotel id %sGoogle does not have a mapping from this parter ID to a Google ID. This could be due to delays in Google's processing or if we were unable to match the partner ID. See documentation on the hotel feed.",In the partner front-end please check the Tools -> Hotel List Feed page for additional information regarding a specific property ID. Contact your TAM if you need additional support
Transaction1023Indicates an internal error at Google.Internal error: Partner name not known. Please report to your TAM.Retry the transmission a limited number times. Failing that, contact your TAM
Transaction1024Google does not have a mapping from this partner ID to a Google ID. This could be due to delays in Google's processing or if we were unable to match the partner ID. See documentation on the hotel feed.Unable to find a Google Hotel ID for partner %s, partner hotel id %sIn the partner front-end please check the Tools -> Hotel List Feed page for additional information regarding a specific property ID. Contact your TAM if you need additional support
Transaction1025In order to be accessed from a RoomBundle, a RoomData must have a RoomID. This RoomData was provided without a RoomID.Cannot store RoomData with an empty RoomID stringEnsure all RoomData have a RoomID
Transaction1026In order to be accessed from a RoomBundle, a PackageData must have a PackageD. This RoomData was provided without a PackageID.Cannot store PackageData with an empty PackageID stringEnsure all PackageData have a PackageID
Transaction1027This indicates incorrect nesting of PartnerData, PropertyData, RoomData, PackageData. None of these should ever nest within another.Unexpected context in finalizing a room dataCheck and fix the XML schema
Transaction1028The arrival date could not be parsed as YYYY-MM-DD.Arrival date %s is invalidFix the formatting
Transaction1029The arrival date is too far into the future. Google will only store arrival dates up to 180 days in advance.Arrival date %s is out of rangeDo not send data for check-in dates too far in the future
Transaction1030The length of stay is beyond what Google stores, which is limited to 14 days.Length of stay %d is out of rangeDo not send data for lengths of stay beyond what Google will store
Transaction1031Google does not have a mapping from this partner ID to a Google ID. This could be due to delays in Google's processing or if we were unable to match the partner ID. See documentation on the hotel feed.Unable to find a Google Hotel ID for partner %s, partner hotel id %sIn the partner front-end please check the Tools -> Hotel List Feed page for additional information regarding a specific property ID. Contact your TAM if you need additional support
Transaction1032To prevent likely data errors, Google does not allow base rates that are empty, negative or more than the maximum nightly price of 10000 USD per night or invalid, empty currency.
  • Did not store Result with invalid base price. Baserate: %f invalid. Partner id %s, check-in %s
  • Did not store Result with invalid base price. Must specify currency. Partner id %s, check-in %s
  • Did not store Result with invalid base price. Currency: %f invalid. Partner id %s, check-in %s
  • Did not store Result with invalid base price. Baserate: %f, length of stay: %lld, currency: %s invalid or exceeds Google limit of %f USD/night. Partner id %s, check-in %s
  • Do not send itineraries that have empty/invalid base rate or currency codes or itineraries with base rates that exceed 10000 USD per night.
    Transaction1033The XML response contains multiple Results with the same property and itinerary.Did not store results due to duplicated key "%s", with identical existing partner hotel id %s and new value %sDo not send duplicated information
    Transaction1034To prevent likely data errors, Google does not allow base rates that are empty, negative or more than the maximum nightly price of 20000 USD per night or invalid, empty currency.
  • Did not store Roombundle with invalid base price. Baserate: %f invalid. Partner id %s, check-in %s
  • Did not store Roombundle with invalid base price. Must specify currency. Partner id %s, check-in %s
  • Did not store Roombundle with invalid base price. Currency: %f invalid. Partner id %s, check-in %s
  • Did not store Roombundle with invalid base price. Baserate: %f, length of stay: %lld, currency: %s invalid or exceeds Google limit of %f USD/night. Partner id %s, check-in %s
  • Do not send itineraries that have empty/invalid base rate or currency codes or itineraries with base rates that exceed 20000 USD per night
    Transaction1035Within a Result, there was no Baserate, but RoomBundles were sent. Google requires a Baserate, which must match the pricing of one of the RoomBundles.Hotel %s, %s %d: Hotel price not available, but room bundles sent; bundles not storedEnsure every Result has a Baserate (and taxes and fees as needed), and that these match one of the RoomBundles
    Transaction1036Within a Result, there was no match between the Result's Baserate and the Baserate of any of the RoomBundles.Hotel %s, %s %d: No room bundle's Baserate matched the Result's Baserate; bundles not stored.Ensure every Result has a Baserate (and taxes and fees as needed), and that these match one of the RoomBundles
    Transaction1037Within a Result, there was no match between the Result's Baserate/Taxes and the Baserate/Taxes of any of the RoomBundles.Hotel %s, %s %d: Room bundles matched the Result's Baserate, but not the Taxes; bundles not storedEnsure every Result has a Baserate (and taxes and fees as needed), and that these match one of the RoomBundles
    Transaction1038Within a Result, there was no match between the Result's Baserate/Taxes/Fees and the Baserate/Taxes/Fees. of any of the RoomBundles.Hotel %s, %s %d: Room bundles matched the baserate and taxes, but not the fees of the hotel price; bundles not storedEnsure every Result has a Baserate (and taxes and fees as needed), and that these match one of the RoomBundles
    Transaction1041A currency code was used that isn't known to Google.Invalid currency code %s given for partner hotel id %sUse only the known values, which are documented in the appropriate tags on the Help Center
    Transaction1042An unknown text value was provided for ChargeCurrency.Unable to interpet %s as a payment typeUse only the known values, which are documented on the Help Center
    Transaction1043Unable to parse the text of Taxes or OTherFees as a float value.Can not parse tax or other fees string: %sCorrect the formatting
    Transaction1045The root element must be Transaction for a file pushed to this path. This is likely caused by responding with a different message type or incorrect path.Unexpected first element %s, expected TransactionCorrect either the file schema or path as appropriate
    Transaction1047Some RoomBundles referenced RoomID or PackageID that are not currently stored at Google. Note: this is not evaluated for PUSH partners. Message details: xx(yy, zz) means that for partner's hotel ID xx, there is missing RoomData or PackageData with IDs yy and zz.Missing or incomplete metadata for ids xx(yy, zz...)If using RoomID or PackageID, ensure the matching metadata is sent prior to use
    Transaction1048The given PointOfSale attribute id's value was not found in the set of defined points of sale.Point of sale ID not found: %sCorrect the value. To update your list of PointsOfSale, send the complete file to the Google e-mail address listed in the Help Center
    Transaction1049An error occurred in pulling the data from the partner. The error message is appended. Note: this does not apply for PUSH partners.Error from POST: %sCheck your logs; ensure Google's IP address is correctly whitelisted. Work with your TAM to verify the hint connection settings
    Transaction1050Within a Result (a property and itinerary), the RatePlanID must be empty or unique for each RoomBundle. The RatePlanID is used as a key. If not given, then Google assigns a unique one. RoomBundle with duplicate RatePlanID %s not storedEnsure RatePlanID are either empty or unique within each Result
    Transaction1051There were Results with the same key in a single XML response. The key is built from the Google Hotel ID, the check-in date and the length of stay. Since the partner hotel ids are different, this is a result of Google's clustering of the two partner hotel IDs to the same Google Hotel ID. This may or may not be incorrect. It requires investigation.Did not store results due to duplicated key "%s", with different existing partner hotel id %s and new value %sInvestigate to determine if these partner IDs represent the same or different properties. If they represent the same property, do not send duplicated information. If this clustering is incorrect, contact your TAM to correct it
    Transaction1052A Query message requests a combination of properties and itineraries. If not all the requested item are returned in the Transaction, then the missing ones are logged with this error. This applies to prices that are pulled.Requested hotel %s, check-in %s, length-of-stay %s not in responseEnsure Transactions contain all requested items in the Query.
    Transaction1053We do not allow Rates tag to be specified anywhere other than inside Result and Roombundle
    Transaction1054We do not allow Rate tag to be specified anywhere other than inside < Rates >
    Transaction1055rate_rule_id' must be specfied for each 'Rate'
    Transaction1056Each Rate can only occur once in a given room bundle or result
    Transaction1057The base rate must be valid for each rate. If you want to drop a specific rate, simply do not send it.
    Transaction1058The XML could not be parsed.Correct the XML such that it passes XML lint or equivalent, including the schema.
    Transaction1059Specific to custom Agoda/Booking XML implementation.
    Transaction1060Use of room_id and/or package_id within a property that have different data, such as name, description or photos.Use unique room_ids where data differs.
    Transaction1061The Transaction message contained unrequested itinerary information. While this could be intentional, it is usually indicative of some error in the returned data. This only applies to pull/hint partners.Ensure the transaction data is correct.
    Transaction1062Every < Result > must specify the < Nights >, with a minimum value of 1, and a current maximum of 14.Supply a valid < Nights > value
    Transaction1063Google maintains a mapping between Google IDs and partner ids. In this case, there are multiple partner IDs for a single Google ID. Google chooses one to be primary. Others will not be recorded.After ensuring the two properties are truly unique and not a case of ID drift, contact your TAM to separate the IDs.
    Bid2001The root element must be Bids for a file pushed to this path. This is likely caused by responding with a different message type or incorrect path.Unexpected first element %s, expected BidsCorrect either the file schema or path as appropriate
    Bid2002The text value for BidRate was not parseable as a float.Cannot parse %s as a float for BidRateCorrect the format
    Bid2003The text value for DailySpendingCap was not parseable as a float.Cannot parse %s as a float for DailySpendingCapCorrect the format
    Bid2004The given value was nota valid currency string. See the BidRate element for a link to the set of accepted values.Invalid currency string: %sEnsure the value is one of the valid values
    Bid2005An unexpected attribute was given. The message shows the known attribute values.Unexpected attribute of BidRate, %s, is not type or currencyInclude only the valid attributes
    Bid2006An unexpected attribute was given. The message shows the known attribute values.Unexpected attribute of DailySpendingCap, %s, is not currencyInclude only the valid attributes
    Bid2007An attribute was given for an element that has no attributes.Attribute %s given for attributeless element %sDo not encode attributes for the given element
    Bid2008A DailySpendingCap must provide both a currency attribute and a text value of the cap.Invalid DailySpendingCap: missing required revenue_cap, has currency

    Invalid DailySpendingCap: has revenue_cap, missing required currency

    Invalid DailySpendingCap: missing required revenue_cap, missing required currency
    Ensure all data is given for the DailySpendingCap
    Bid2009"default' bids may not specify a rate or currency. "fixed" bids must have a valid rate (>0)and a currency. "percentage" bids must have a valid rate (0-100) and no currency.Incorrect bid type specificationsEnsure the correct data is given for the bid type
    Bid2010The site string is not valid. See the Help Center for allowed values.Invalid site string: %sChoose from one of the allowed values
    Bid2011The country string is not a recognized country.Invalid country string: %sChoose from one of the allowed values
    Bid2012The device type string may only be mobile. All other types are part of the base bid.Invalid device type string: %sDo not specify device type other than mobile
    Bid2013The MinStayNights text could not parsed as an integer, was negative or the MinStayNights had already been specified.Invalid min_stay_nights: %sFix the formatting to comply with all the rules
    Bid2014The multiplier value could not be parsed as a float.Invalid multiplier: %sFix the formatting
    Bid2015A bid multiple must contain exactly one constraint, chosen from: site, user country, length of stay, device type. Further, the multiplier value must be between 0.0 and 10.0.BidMultiplier(s) over or under specified. Must have exactly one constraint per multiplierFix the BidMultiplier to comply with the rules
    Bid2016A bid type of "default" may not be used on or after July 23, 2014.Bid type 'default' is no longer supportedChange any "default" bids to be "fixed" or "percentage" bids
    Bid2017The XML could not be parsed.Correct the XML such that it passes XML lint or equivalent, including the schema.
    Bid2018The timestamp attribute could not be parsed. It will use the time the file was uploaded.
    Bid2019The bid multiplier value is out of range. Should be between 0.0 and 10.0.Fix the bid multiplier value to one that is valid.
    Bid2020Among all the bid multipliers specified on the same properties, the values for the same multiplier type should be unique so at most one of them can be applied at a time.Fix the bid multipliers of the given type so that there are no duplicates.
    Bid2021The MinDays text could not be parsed as an integer, was negative, was larger than 180, or the MinDays had already been specified.Fix the formatting to comply with the rules.
    Bid2022The DayOfWeek text could not be recognized.Fix the formatting to comply with the rules.
    Bid2023Too many advance booking window multipliers are specified. Hotel Ads supports up to 10 advance booking window multipliers for each property.Fix the formatting to comply with the rules.
    Bid2024The text value for MaximumBidCap could not be parsed as a positive float value.Correct the format.
    Bid2025An unexpected attribute was given. The message shows the known attribute values.Include only the valid attributes.
    Bid2026The given value was not a valid currency string. See the BidRate element for a link to the set of accepted values.Ensure the value is one of the valid values.
    Bid2027A MaximumBidCap must provide both a currency attribute and a text value of the cap.Ensure all data is given for the MaximumBidCap.
    Bid2028The given value was not a valid type string for Property. Allowed values: ""hotel"", ""group"", or ""account_default"".Ensure the value is one of the valid values.
    Bid2029An unexpected attribute was given. The message shows the known attribute values.Include only the valid attributes.
    Bid2030A Property with type ""hotel"" is missing a hotel name.Include a hotel name.
    Bid2031A Property with type ""group"" is missing a group name.Include a group name.
    Bid2032A Property with type ""account_default"" specified a value when there shouldn't be one.Don't include a value for type account_default.
    Bid2033None of the Properties specified were valid.Ensure that at least one valid Property is specified.
    Bid2034A "percentage" bid was missing the rate, or the rate is outside of the range of 0.0 - 100.0.Fix the bid value to one that is valid.
    Bid2035A "fixed" bid was missing the rate or currency, or the rate was less than the minimum (0.0).Fix the bid value to one that is valid.
    Hint3001The root element must be Hint for a file pushed to this path. This is likely caused by responding with a different message type or incorrect path.Expected first element of Hint, got %sCorrect either the file schema or path as appropriate
    Hint3002The FirstDate text was not parseable as a date. It should be YYYY-MM-DD.Invalid FirstDate: %sCorrect the format
    Hint3003The LastDate text was not parseable as a date. It should be YYYY-MM-DD.Invalid LastDate: %sCorrect the format
    Hint3004The CheckInDate text was not parseable as a date. It should be YYYY-MM-DD.Invalid CheckInDate: %sCorrect the format
    Hint3005The text value for LengthOfStay was not parseable as an integer.Invalid LengthOfStay: %sCorrect the format
    Hint3006The Item/Stay was missing either the CheckInDate or a valid length of stay. The message shows which ones are missing.Item with Stay missing required element(s), skipping: CheckInDate: %s, LengthOfStay: %sAdd the necessary elements
    Hint3007The Item/StaysIncludingRange was missing the required FirstDate.Item with StaysIncludingRange missing FirstDateAdd the necessary elements
    Hint3008The Item was missing at least one of the 2 required elements. The message shows which ones are missing.Item missing required element(s), skipping: FirstDate: %s LastDate: %sAdd the necessary elements
    Hint3009Google's parser enforces an upper limit on length of stay to reduce data errors. Currently this is 40 days, but we currently only store values up to 14 days.LengthOfStay too long: %d Max: %d. Skipping Item: Property: %s CheckInDate: %s LengthOfStay: %dDo not send itineraries with length of stay > 14 days, or correct the value
    Hint3010We drop data for itineraries that have past. This check is applied immediately after receiving data from the partner, so is not a function of latency. These errors should be fixed by the partner.CheckInDate %s before yesterday %s. Skipping Item: Property: %s CheckInDate: %s LengthOfStay: %dDo not send itineraries with check-in days in the past
    Hint3012When giving a FirstDate and LastDate, the LastDate must be greater than or equal to the FirstDate.FirstDate %s is after LastDate %sAdjust the FirstDate and LastDate as appropriate
    Hint3013Google will not store an itinerary with a check-in date more than 180 days in the future.FirstDate %s is more than %d days outDo not send itineraries too far in advance
    Hint3014Google will adjust any LastDate to be no more than 180 days in advance.LastDate %s is more than %d days outDo not send itineraries too far in advance
    Hint3015An error occurred in pulling the data from the partner. The error message is appended.Error in POST: %sCheck your logs; ensure Google's IP address is correctly whitelisted. Work with your TAM to verify the hint connection settings
    Hint3016ErrGoogle does not have a mapping from this partner ID to a Google ID. This could be due to delays in Google's processing or if we were unable to match the partner ID.In the partner front-end please check the Tools -> Hotel List Feed page for additional information regarding a specific property ID. Contact your TAM if you need additional support
    Hint3017The LastDate must be today or later.LastDate is too earlyDo not send hints for ranges that have passed out of date
    Hint3018None of the provided hotel ids (if any) could be translated to google IDs.Item with Stay missing valid partner hotel IDs, skippingEnsure the IDs are valid and match those in the hotel feed
    Hint3019ErrItem with StaysIncludingRange missing valid hotel ids, skipping
    Hint3020ErrItem missing valid hotel ids, skipping
    Hint3021ErrThe XML could not be parsedCorrect the XML such that it passes XML lint or equivalent, including the schema.
    Hint3022ErrAn error occurred in pulling the data from the partner. The error message is appended.Check your logs; ensure Google's IP address is correctly whitelisted. Work with your TAM to verify the hint connection settings.
    Hotel info4001Storing of hotel information is enabled separately from standard prices. Your account has not been enabled for storing this data. Note that storing can be enabled without serving. Partner %s is not enabled for storing of room data. Please contact your TAM.Contact your TAM to activate storage.
    Hotel info4002The timestamp attribute did not conform to Google's requirements. Note that our required format varies slightly from the generally accepted format. We do not accept the fractional seconds.Unable to parse time stamp: %sCorrect the timestamp formatting
    Hotel info4003The XML root element was incorrect for a file pushed on this path.Unexpected first element %s, expected HotelInfoFeedCorrect either the first element or the path as appropriate
    Hotel info4004The value of Occupancy or Capacity is above Google's limit. The limit was chosen to avoid unlikely error values, though there are some rooms that exceed this limit.Will not use occupancy/capacity %d, which is over the limit %dCorrect if the value, if possible. If the actual value is above the limit, either remove the value or set it at the limit. If removing it, ensure the description text provides this information
    Hotel info4005Unparseable number provided.Unable to interpret %s as a number for occupancy or capacityFix the formatting
    Hotel info4006Unparseable boolean provided. Accepted values are: 0, 1, true, false.Unable to interpret %s as a booleanFix the formatting
    Hotel info4007Google sets a limit on maximum refundable days, mostly to avoid incorrect data.Will not use %d refund days, which is greater than limit %dCorrect the value, if possible. If the actual value is above the limit, code this room as non-refundable
    Hotel info4008Unparseable number provided.Unable to understand %s as a number for refundable daysFix the formatting
    Hotel info4009Unparseable time provided.Unable to understand %s as HH:MMFix the formatting
    Hotel info4010Google does not have a mapping from this partner ID to a Google ID. This could be due to delays in manifest processing, or if the matching failed. See documentation on the hotel feed.Cannot store data for partner %s, property %s; there is no matching Google hotel idEnsure all necessary information for matching is provided in the hotel feed. Contact your TAM to investigate specific IDs
    Hotel info4011Unparseable number provided.Unable to parse as a number: %s for BaserateFix the formatting
    Hotel info4012Unparseable number provided.Invalid boolean value for all_inclusive: %sFix the formatting
    Hotel info4013The currency code given was not one Google recognizes.Invalid currency: %sProvide a valid currency code
    Hotel info4014Unparseable number provided.Can not parse tax and fees string: %sFix the formatting
    Hotel info4015The accepted values are: web, hotel and deposit.Unrecognized payment type: %sProvide an accepted value
    Hotel info4016An internal error has occurred.Internal error: Unable to finalize with empty partner: %sRetry the transmission a limited number times. Failing that, contact your TAM
    Hotel info4017Google does not have a mapping from this partner ID to a Google ID. This could be due to delays in manifest processing, or if the matching failed. See documentation on the hotel feed.Could not find google hotel id for partner hotel id: %s, partner %s, id %sEnsure all necessary information for matching is provided in the hotel feed. Contact your TAM to investigate specific IDs
    Hotel info4018In order to be accessed from a RoomBundle, a RoomData must have a RoomID. This RoomData was provided without a RoomID.Empty room_id string in room_data: %sEnsure all RoomData have a RoomID
    Hotel info4019An internal error has occurred. This could also be caused by unusual XML structure.Internal error: Unable to finalize without context: %sRetry the transmission a limited number times. Failing that, contact your TAM
    Query Control5001One or more of the Item elements in the QueryControl was missing the required Property element. QueryControl did not evaluate. One or more Items lacked a Property id: %sEnsure all Items contain a Property.
    Validate against the schema
    Query Control5002The root element must be QueryControl for a file pushed to this path. This is likely caused by responding with a different message type or incorrect path.Unexpected first tag: %sCorrect either the file schema or path as appropriate
    Query Control5003An unknown XML element was seen in the response.Found unexpected element: %sValidate against the schema
    Query Control5004Text was seen within an Item element, and it should not be present.Found unexpected text inside an Item: %sRemove any excess text within the Item elements
    Query Control5005Text was seen within the QueryControl element, and it should not be present.Found unexpected text inside an QueryControl: %sRemove any excess text within the QueryControl element
    Query Control5006XML attributes were found in the response. The QueryControl message does not use attributes.Unexpected attributes in query control XML: %sRemove all attributes. Validate against the schema
    Query Control5007The text for MaxAdvancePurchase could not be parsed into an integer value.Could not parse max advance purchase days text: %sCheck the text value of the MaxAdvancePurchase elements. Validate against the schema
    Query Control5008The text for MaxLengthOfStay could not be parsed into an integer value.Could not parse length of stay text: %sCheck the text value of the MaxLengthOfStay elements. Validate against the schema
    Query Control5009Before accepting a new QueryControl message, the existing message is compared for size. This error indicates an internal error in reading the existing message.Internal error: Could not parse existing QueryControl messageContact your TAM to help clear the error.
    Query Control5010Before accepting a new QueryControl message, the existing message is compared for size. This error indicates the new message differs enough in size from the existing message to raise concern. This could be due to many causes, but the control is to prevent accepting a new QueryControl that might be missing large numbers of properties.Will not store QueryControl with large change in QueryControl size. Existing: %d; new: %dContact your TAM to override the control and force acceptance after verification of the new QueryControl
    Query Control5011When a new QueryControl message removes properties or itineraries compared to the previous ones, those values must be removed from the pricing table. If the existing file contains property IDs that are no longer supported, this error can occur.Internal Error: Could not find google hotel id for partner hotel id: %s found in prior QueryControl and not in new QueryControlThere is no user action required
    Query Control5012An internal error occurred. It is possible that a QueryControl transaction was not made on schedule. Internal error: Unable to parse task data: %sContact your TAM
    Query Control5013An internal error occurred. It is possible that a QueryControl transaction was not made on schedule. Internal error: Unsupported task type: %sContact your TAM
    Query Control5014An error occurred in fetching the QueryControl response from the partner.Error in POST: %sLook at internal error logs. If IP addresses have changed, they must be communicated to your TAM
    Query Control5015Text was seen within the HintControl element, and it should not be present.Found unexpected text inside a HintControl: %sRemove any excess text within the HintControl element
    Query Control5016The text for the MultipleItineraries was not given in the response.MultipleItineraries given with empty textEnsure a valid MultipleItineraries text value is given.
    Query Control5017The text for the MultipleItineraries was not one of the allowed values. Unknown value for MultipleItineraries: %sEnsure a valid MultipleItineraries text value is given.
    Query Control5018Google does not have a Google Hotel ID for the given partner's property ID. Will not store QueryControl for id %s, no Google Hotel IDIf the partner ID is correct, contact your TAM to address any issues with the Hotels Feed
    Query Control5019The XML could not be parsed. Will not store QueryControl for id %s, no Google Hotel IDCorrect the XML such that it passes XML lint or equivalent, including the schema.
    Push Result6001An internal error has occurred. Internal error: Bad status code: %sRetry the transmission a limited number times. Failing that, contact your TAM
    Push Result6002The transmission was rejected the entire files was not supplied in a single POST. Though HTTP supports upload via multiple posts, it is not supported for this application. Internal error: %s not single post protocolEnsure your transmission uploads the entire file in a single POST
    Push Result6003An internal error has occurred. Internal error: No file name extracted from: %sRetry the transmission a limited number times. Failing that, contact your TAM
    Push Result6004An internal error has occurred. Internal error: Client address %s is not recognized or permitted. Feed type: %s Partner: %sRetry the transmission a limited number times. Failing that, contact your TAM
    Push Result6005The upload path did not match any of the accepted paths. Upload path not recognized: %sCorrect the upload path. The paths are documented on the developer site
    Push Result6006For security, HPA keeps a list of accepted IPs and matching partners. A message came in either from an unknown IP or from a known IP but not an allowed partner for that IP. Partner %s not allowed from IP %s Partner %s not allowed from IP %s, but these partners are: %sEnsure the partner attribute is correct in the message and that it was uploaded from one of the IPs communicated to Google. Contact your TAM to update the list of IPs
    Push Result6007Err (HTTP - 400) Could not extract OTA information from OTA message
    Push Result6008The uploaded file did not contain a partner attribute, and the partner could not be deduced from the IP address. No partner tag in file, and no partner with this IP: %sAdd the partner attribute, check your sending IP address. Contact your TAM to change your list of IP addresses
    Push Result6009The partner name provided in the partner attribute is not a known partner. Do not recognize the partner: %sCheck the spelling of the transmitted partner name. Contact your TAM to your exact partner name
    Push Result6010An internal error occurred after accepting your job. Internal error: Failed to create queue file to add task to task master for partner: %s, filename: %sRetry the transmission a limited number times. Failing that, contact your TAM
    Push Result6011An internal error occurred after accepting your job. Internal error: Failed to rename: %s to: %s status: %s Request: %sRetry the transmission a limited number times. Failing that, contact your TAM
    Push Result6012An internal error occurred after accepting your job. Internal error: Failed to create directory for %s: %sRetry the transmission a limited number times. Failing that, contact your TAM
    Push Result6013Before acceptance, the file is parsed by a generic XML parser. The parsing failed, so the file is not well formed XML. Parse error in uploaded XML
    Parse error in uploaded XML from partner: %s
    Ensure the file passes xmllint or equivalent XML validity checker
    Push Result6014A file was sent that did not contain a partner attribute. When there is only one partner at a given IP address, we can infer the partner from the IP address. In this case there are multiple partners at the same IP, so the partner cannot be inferred. No partner tag in file, and multiple partners with this IP: %sProvide a partner tag. If the IP address is not supposed to be by any other partner, contact your TAM to investigate
    Push Result6015A Transaction file was pushed for a partner configured for pull or hint modes.Transaction PUSH not authorized for partner: %sContact your TAM to change your transmission mode
    Push Result6016An internal error occurred after accepting your job.Internal error: Parse file not found, and no partner with this IP: %sRetry the transmission a limited number times. Failing that, contact your TAM
    Push Result6017An internal error occurred after accepting your job.Internal error: Parse file not found, and multiple partners with this IP: %sRetry the transmission a limited number times. Failing that, contact your TAM
    Push Result6018The file was not processed since the partner is not active.Partner not active: %sContact your TAM to activate your feed
    Push Result6027Missing partner's name attribute in the file.A file was sent that did not contain a partner attribute. Though we can infer the partner from the IP address, this will soon be required.Provide a partner attribute. If you are unsure what the partner's attribute should be, ask your Technical Account Manager (TAM).
    OTA Push8001The partner configuration is incorrect. The error message should indicate what is missing.Configuration Error: %s The partner configuration is incorrect. The error message should indicate what is missing
    OTA Push8002There was an error reading the pushed file.Error reading file: %s There was an error reading the pushed file from colossus. Please alert eng
    OTA Push8003There was an error parsing the XML file.Error parsing XML There was an error parsing the XML file. Check the contents of the associated file to make sure the partner is sending proper XML
    OTA Push8004The XML was parseable, but the message included inside is not one we know how to understand.Error understanding XML message Confirm the XML has correct formatting, reach out to your TAM if you have additional questions.
    OTA Push8005We were able to determine the XML was a valid OTA message, but we do not know how to parse this particular one. We can only parse OTA_HotelAvailNotifRQ and OTA_HotelRateAmountNotifRQ.Unsupported OTA message: %s We were able to determine the XML was a valid OTA message, but we do not know how to parse this particular one. We can only parse OTA_HotelAvailNotifRQ and OTA_HotelRateAmountNotifRQ
    OTA Push8006We were unable to parse the AvailStatusMessage with the given index, as no RestrictionStatus was present.Unable to find RestrictionStatus for AvailStatusMessage[%d] We were unable to parse the AvailStatusMessage with the given index, as no RestrictionStatus was present
    OTA Push8007We were unable to process the AvailStatusMessage with the given index as we did not recognize the value of the RestrictionStatus (given in the error message)Unknown RestrictionStatus for AvailStatusMessage[%d]: %s We were unable to process the AvailStatusMessage with the given index as we did not recognize the value of the RestrictionStatus (given in the error message)
    OTA Push8008We were unable to process the AvailStatusMessage with the given index as we did not recognize the value of the Restriction attribute (given in the error message)Unknown Restriction for AvailStatusMessage[%d]: %s We were unable to process the AvailStatusMessage with the given index as we did not recognize the value of the Restriction attribute (given in the error message)
    OTA Push8009We were unable to parse the minimum LOS for the AvailStatusMessage with the given index.Failed to parse min LOS for AvailStatusMessage[%d]: %s We were unable to parse the minimum LOS for the AvailStatusMessage with the given index
    OTA Push8010We were unable to parse the maximum LOS for the AvailStatusMessage with the given index.Failed to parse max LOS for AvailStatusMessage[%d]: %s We were unable to parse the maximum LOS for the AvailStatusMessage with the given index
    OTA Push8011We were unable to parse the minimum LOS for the AvailStatusMessage with the given index.Failed to parse min LOS for AvailStatusMessage[%d]: %s Same as 8010, but separate code to indicate different parsing logic
    OTA Push8012We were unable to parse the maximum LOS for the AvailStatusMessage with the given index.Failed to parse max LOS for AvailStatusMessage[%d]: %s Same as 8010, but separate code to indicate different parsing logic
    OTA Push8013The minimum LOS was greater than the maximum LOS for the AvailStatusMessage with the given index.Min LOS (%d) > Max LOS (%d) for AvailStatusMessage[%d] The minimum LOS was greater than the maximum LOS for the AvailStatusMessage with the given index
    OTA Push8014The given RateAmountMessage could not be processed as it was missing the StatusApplicationControl element.Failed to parse status application control in RateAmountMessage[%d] The given RateAmountMessage could not be processed as it was missing the StatusApplicationControl element
    OTA Push8015The given XML element was missing the AmountBeforeTax attributeFailed to find AmountBeforeTax in RateAmountMessage[%d]/BaseByGuestAmt[%d] The given XML element was missing the AmountBeforeTax attribute
    OTA Push8016Could not find a currency for the given XML element in the RateAmountMessage.Unable to find a CurrencyCode for RateAmountMessage[%d]/BaseByGuestAmt[%d], and no default currency is set Could not find a currency for the given XML element in the RateAmountMessage
    OTA Push8017Could not parse the nightly rate given in the specified XML element. The string at the end of the message is the value we got in the XML.Unable to parse nightly rate for RateAmountMessage[%d]/BaseByGuestAmt[%d]: %s Could not parse the nightly rate given in the specified XML element. The string at the end of the message is the value we got in the XML
    OTA Push8018The Taxes/Fees XML was malformed, and we were unable to pass the given attribute.Could not obtain %s %s attribute at property index %d, tax/fee index %d The Taxes/Fees XML was malformed, and we were unable to pass the given attribute
    OTA Push8019We could not parse the Tax/Fee amount from the XML.Could not parse %s amount attribute at element %d from: %s We could not parse the Tax/Fee amount from the XML
    OTA Push8020We were unable to parse the basis attribute for the given Tax/FeeCould not parse %s basis attribute at element %d from: %s We were unable to parse the basis attribute for the given Tax/Fee
    OTA Push8021We were unable to parse the period attribute for the given Tax/FeeCould not parse %s period attribute at element %d from: %s We were unable to parse the period attribute for the given Tax/Fee
    OTA Push8022We were unable to set a currency either from parsing from the XML or from the partner config, for the given Tax/Fee element.Unable to parse a currency (or get one from config) for %s[%d] We were unable to set a currency either from parsing from the XML or from the partner config, for the given Tax/Fee element
    OTA Push8023Could not parse the type attribute for the given Tax/FeeCould not parse %s type attribute at element %d from: %s Could not parse the type attribute for the given Tax/Fee
    OTA Pull7001There was an error during POSTError from POST: %s Check your logs; ensure Google's IP address is correctly whitelisted. Work with your TAM to verify the OTA connection settings
    OTA Pull7002There was an error getting the partner configurationError getting partner configuration for %s Please contact your TAM for them to check that the partner configuration exists for you
    OTA Pull7003There was an error getting the partner configurationError getting OTA Pull configuration for %s Please contact your TAM for them to check check that the ota_xml_pull_configuration field is configured in the protocol configuration
    OTA Pull7004We were unable to parse the XML message as it was malformed.Error parsing XML message Run xmllint to validate your XML
    OTA Pull7005The RoomStay element with the given index did not have a property id set (and no global property was defined in the message).Could not determine a hotel id for RoomStay[%d] Please check the property ID
    OTA Pull7006Our hotels manifest has no corresponding record for the hotel id provided by the partner.Cannot find google hotel id for partner hotel id %s Please confirm the hotel has been clustered
    OTA Pull7007One of the elements in the XML message has elements with different currencies. We don't support this, so we ignore the elements.A RoomRate element has multiple currencies in its Rate elements Please change your XML to use one currency.
    OTA Pull7008Unable to parse the price before taxes from the XML message. The string that we got is given.Unable to parse price before taxes: %s Please fix the price.
    OTA Pull7009Unable to parse the price after taxes from XML message. The string that we got is given.Unable to parse price after taxes: %s Please fix the price.
    OTA Pull7010Unable to parse the taxes from the XML message. The string that we got is given.Unable to parse taxes: %s Please fix the taxes.
    OTA Pull7011The dates given for a element are not parseable. The Effective and Expire dates are given as they appear in the XML (could be empty)Error parsing date range for rate. Effective: %s, Expire: %s Please fix the date.
    OTA Pull7012We only support "Day" and "FullDuration" as time units for elements, where "Day" means the rate applies per day, while "FullDuration" means the rate applies for the entire given date range.Unsupported time unit: %s Please change your time unit.
    OTA Pull7013The base price in the OTA XML message cannot be parsed. Either the message is wrong, or the code needs to be updated to support a new format.Contact your TAM.
    OTA Pull7014The total price (base + taxes/fees) in the OTA XML message cannot be parsed. Either the message is wrong, or the code needs to be updated to support a new format.Contact your TAM.
    OTA Pull7015We were unable to parse any price in the OTA XML message. Either the message is wrong, or the code needs to be updated to support a new format.Contact your TAM.
    OTA Pull7016Your OTA XML messages did not contain currency codes, and the partner configuration does not specify a default currency to use.Contact your TAM to have them fix the partner config or make sure you are sending us currency info.
    OTA Pull7017The nightly breakdown given in TPA_extensions doesn't match the amounts given in other elements. The amount from the other elements was used.Please adjust the TPA_Elements breakdown.
    OTA Pull7018Unable to parse the fees from the XML message. The string that we got is given.Please fix the fees.
    OTA Pull7019This is a warning received in the XML response.
    OTA Pull7021There was no success element returned
    Warn1064When RoomData or PackageData is placed directly in a RoomBundle, a supplied RoomId should be in the RoomData or PackageData.RoomId in RoomBundle not equal to RoomId in contained RoomData.Remove the RoomID from the RoomBundle in favor of the one contained in the RoomData or PackageData.
    Warn1065Name, Description and PhotoURL should be in a RoomData, not a RoomBundle.Name/ Description/ PhotoURL in a RoomBundle.Create a contained RoomData with the elements. If possible, send it independently of each itinerary and only refer to it from the itinerary. 
    Warn1066Every Roombundle must have a RatePlanID element, although it can have an empty value, in which case a value is assigned.No RatePlanID element seen in a RoomBundle.In most cases, the URL needs the RatePlanID. Some partners may make do with custom fields. If really not needed, insert an empty field.
    Warn1067Every RoomData must have a RoomID within it. Every PackageData must have a PackageID within it. The values can be empty, allowing Google to assign a random value.RoomData or PackageData given without an internal RoomID or PackageID.If not needed for URL generation, add to every RoomData, and similarly for PackageData.