Feed Status Error Messages

If you received a Feed Status error message, click on the links below to jump to the relevant section that contains your error message, its description, and action you can take.
Find your error message
1001-1050 1051-2000 2001-2050
2051-3000 3001-3022 4001-4022
5001-5023 6001-6028 7000-7021
8001-8028 10000-10025 9000001-9000008
Code Message Description Action
1001 Timestamp "$0" not in format "YYYY-MM-DDTHH:MM:SS<+|->HH:MM" or "YYYY-MM-DDTHH:MM:SSZ". The timestamp format is very specific. It requires the timezone offset or Z, and it does not accept fractional seconds. Correct the format.
1002 Invalid currency code in converting Taxes from $0 to $1. The currency code was not a valid one. See the Help Center document for allowed currency codes. Use a valid currency code.
1003 Invalid currency code in converting OtherFees from $0 to $1. The currency code was not a valid one. See the Help Center document for allowed currency codes. Use a valid currency code.
1004 Internal error: Invalid availability result for partner $0, $1 This indicates an internal error during processing. Please contact your TAM.
1005 Invalid taxes and fees for partner: $0, $1 This occurs from any of: invalid baserate currency, no Baserate, invalid Taxes currency, invalid OtherFees currency. Ensure valid currency codes, and a baserate exists for all prices.
1006 All inclusive specified, but taxes provided for partner: $0, $1 The "all inclusive" flag indicates that taxes and fees could not be separated from the baserate, but this itinerary also contained a value for taxes. If taxes are known, correctly separate baserate from taxes and do not report all_inclusive.
1007 is expected only as immediate child of , but found elsewhere. This indicates a Result tag was seen somewhere unexpected. Ensure Result is only given as a child of Transaction.
1008 RoomID outside of RoomData/RoomBundle context. This indicates a RoomID tag was seen in an inappropriate context. Ensure RoomID is only used where indicated.
1009 PackageID outside of PackageData/RoomBundle context. This indicates a PackageID tag was seen in an inappropriate context. Ensure PackageID is only used where indicated.
1010 Use of RatePlanID within RoomData/PackageData is not stored. This indicates a RatePlanID was seen in an inappropriate context. RatePlanID is only valid in a RoomBundle. Do not use RatePlanID outside of allowed contexts.
1011 Capacity/Occupancy outside of a RoomBundle/RoomData/PackageData not stored. This indicates a Capacity or Occupancy was seen in an inappropriate context. Occupancy/Capacity are only appropriate in a RoomBundle, RoomData or PackageData.
1012 Will not use Capacity/Occupancy of $0, which is over Google limit of $1. To prevent likely data errors, Google limits the maximum capacity or occupancy to 20. Do not send capacity or occupancy information that exceeds 20.
1013 Unable to interpret $0 as a number for occupancy/capacity. The text value for occupancy or capacity could not be parsed as an integer. Correct the format.
1014 Unable to interpret $0 as a boolean. Unparseable boolean provided. Accepted values are: 0, 1, true, false. Correct the format.
1015 XML text "$0" provided in XML element $1 not in schema. Text was provided for an element that does not accept text. Remove the text.
1016 Use of outside of an appropriate context ignored. The Text element (as opposed to text value) was used in an inappropriate context. Find the correct context and relocate or remove the .
1017 Use of outside of an appropriate context ignored. The Refundable element was used in an inappropriate context. It is usable in RoomBundle, RoomData and PackageData. It is not allowed directly in Result. Find the correct context and relocate or remove the .
1018 Will not use $0 refund days, which is greater than Google limit $1. Google sets a limit on maximum refundable days, mostly to avoid incorrect data. Correct the value, if possible. If the actual value is above the limit, code this room as non-refundable.
1019 Unable to understand $0 as a number for refundable days. Unparseable number provided. Fix the formatting.
1020 Unable to understand $0 as HH:MM. Unparseable time provided. Fix the formatting.
1021 XML Element $0 has no attribute named $1 to give value $2. The named element does not accept attributes. Remove attributes for this element.
1022 Unable to find a Google Hotel ID for partner $0, partner hotel id $1. Google 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. In the Hotel Ads Center please check the Tools -> Hotel List -> Matching Report page for additional information regarding a specific property ID. Contact your TAM if you need additional support
1023 Partner name not known. Please report to your TAM. Indicates an internal error at Google. Retry the transmission a limited number times. Failing that, contact your TAM.
1024 Unable to find a Google Hotel ID for partner $0, partner hotel id $1. Google 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. In the Hotel Ads Center please check the Tools -> Hotel List -> Matching Report page for additional information regarding a specific property ID. Contact your TAM if you need additional support
1025 Cannot store RoomData with an empty RoomID string. In order to be accessed from a RoomBundle, a RoomData must have a RoomID. This RoomData was provided without a RoomID. Ensure all RoomData have a RoomID.
1026 Cannot store PackageData with an empty PackageID string. In order to be accessed from a RoomBundle, a PackageData must have a PackageD. This RoomData was provided without a PackageID. Ensure all PackageData have a PackageID.
1027 Unexpected context in finalizing a room data. This indicates incorrect nesting of PartnerData, PropertyData, RoomData, PackageData. None of these should ever nest within another. Check and fix the XML schema.
1028 Arrival date $0 is invalid. The arrival date could not be parsed as YYYY-MM-DD. Fix the formatting.
1029 Arrival date $0 is out of range. The arrival date is out of range (possibly in the past). Do not send data for check-in days in the past.
1030 Length of stay $0 is out of range. The length of stay is beyond what Google stores, which is limited to 30 days. Do not send data for lengths of stay beyond what Google will store.
1031 Unable to find a Google Hotel ID for partner $0, partner hotel id $1. Google 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. In the Hotel Ads Center please check the Tools -> Hotel List -> Matching Report page for additional information regarding a specific property ID. Contact your TAM if you need additional support
1032 Did not store Result with invalid base price. $0. Partner id $1, check-in $2, length of stay $3. To 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. Do not send itineraries that have empty/invalid base rate or currency codes or itineraries with base rates that exceed 10000 USD per night.
1033 Did not store results due to duplicated key "$0", with identical existing partner hotel id $1 and new value $2. The XML response contains multiple Results with the same property and itinerary. Do not send duplicated information.
1034 Hotel $0, $1 $2: Invalid price $3 $4 for Room Bundle $5. $6 To prevent likely data errors, Google does not allow RoomBundle base rates that are empty, negative or more than the maximum nightly price of 20000 USD per night or invalid, empty currency. Do not send itineraries that have empty/invalid base rate or currency codes or itineraries with base rates that exceed 20000 USD per night.
1035 $0: Hotel price not available, but room bundles sent; bundles not stored. Within a Result, there was no Baserate, but RoomBundles were sent. Google requires a Baserate, which must match the pricing of one of the RoomBundles. Ensure every Result has a Baserate (and taxes and fees as needed), and that these match one of the RoomBundles.
1036 $0: No room bundle's matched the 's ; bundles not stored. Within a Result, there was no match between the Result's Baserate and the Baserate of any of the RoomBundles. Ensure every Result has a Baserate (and taxes and fees as needed), and that these match one of the RoomBundles.
1037 $0: Room bundles matched the 's , but not the ; bundles not stored. Within a Result, there was no match between the Result's Baserate/Taxes and the Baserate/Taxes of any of the RoomBundles. Ensure every Result has a Baserate (and taxes and fees as needed), and that these match one of the RoomBundles.
1038 $0: Room bundles matched the baserate and taxes, but not the fees of the hotel price; bundles not stored. Within a Result, there was no match between the Result's Baserate/Taxes/Fees and the Baserate/Taxes/Fees. of any of the RoomBundles. Ensure every Result has a Baserate (and taxes and fees as needed), and that these match one of the RoomBundles.
1039 $0: Closest Room bundle did not match 's currency. Within a Result, there was no match between the Result's Currency and the Currency of the roombundles. Ensure the currency used for the Result and its matching Room Bundle is the same.
1040 $0: Closest Room bundle did not match the Result's eligibility. All Room bundles dropped. Within a Result, the closest matching Room Bundle's availability did not match that of the Result. Ensure the availability of the Result matches the availability of its matching Roombundle.
1041 Invalid currency code $0 given for partner hotel id $1 A currency code was used that isn't known to Google. Use only the known values, which are documented in the appropriate tags on the Help Center.
1042 Unable to interpet $0 as a payment type. An unknown text value was provided for ChargeCurrency. Use only the known values, which are documented on the Help Center.
1043 Can not parse tax or other fees string: $0 Unable to parse the text of Taxes or OtherFees as a float value. Correct the formatting.
1045 Unexpected first element $0, expected Transaction. The 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. Correct either the file schema or path as appropriate.
1047 Missing or incomplete metadata for ids $0 Some 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. If using RoomID or PackageID, ensure the matching metadata is sent prior to use.
1048 Point of sale ID not found: $0 The given PointOfSale attribute id's value was not found in the set of defined points of sale. Correct the value. To update your list of PointsOfSale, send the complete file to the Google e-mail address listed in the Help Center.
1049 Error from POST: $0 An error occurred in pulling the data from the partner. The error message is appended. Note: this does not apply for PUSH partners. Check your logs; ensure Google's IP address is correctly whitelisted. Work with your TAM to verify the hint connection settings.
1050 RoomBundle with duplicate RatePlan ID $0 not stored. Within 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. Ensure RatePlanID are either empty or unique within each Result.
1051 Did not store results due to duplicated key "$0", with different existing partner hotel id $1 and new value $2. There 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. Investigate 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.
Code Message Description Action
1053 Rates is expected only as immediate child of Result or RoomBundle tag, but it was found elsewhere. We do not allow Rates tag to be specified anywhere other than inside Result and Roombundle
1054 Rate is expected only as immediate child of Rates tag, but it was found elsewhere. We do not allow Rate tag to be specified anywhere other than inside Rates
1055 Rate must specify 'rate_rule_id'. rate_rule_id' must be specfied for each 'Rate' Please ensure you have provided a rate_rule_id for every Rate Provided.
1056 Rate with duplicate 'rate_rule_id' $0 not stored. Each Rate can only occur once in a given room bundle or result
1057 Hotel $0, $1 $2: Invalid price $3 $4$5 The base rate must be valid for each rate. If you want to drop a specific rate, simply do not send it.
1058 XML parsing failure$0 The XML could not be parsed. Correct the XML such that it passes XML lint or equivalent, including the schema.
1060 Mismatch of metadata for property $0, package/room id $1. Use 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.
1061 Unexpected receipt of itineraries (hotel, check-in, length-of-stay): $0 The 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.
1062 either not specified or out of range. Every must specify the , with a minimum value of 1, and a current maximum of 30. Supply a valid value
1063 For partner $0, found (partner_hotel_id, google_id) where partner hotel id is non-primary match for Google ID: $1 Google 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 I D drift, contact your TAM to separate the IDs.
1064 RoomId $0 in RoomBundle not equal to RoomId $1 in contained RoomData. When RoomData or PackageData is placed directly in a RoomBundle, a supplied RoomId should be in the RoomData or PackageData. Remove the RoomID from the RoomBundle in favor of the one contained in the RoomData or PackageData.
1065 Name/Description/PhotoURL in a RoomBundle. Name, Description and PhotoURL should be in a RoomData, not 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.
1066 No RatePlanID element seen in a RoomBundle. Every Roombundle must have a RatePlanID element, although it can have an empty value, in which case a value is assigned. In most cases, the URL needs the rate plan id. Some partners may make do with Custom fields. If really not needed, insert an empty .
1067 RoomData or PackageData given without an internal RoomID or PackageID. Every 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. If not needed for URL generation, add to every RoomData, and similarly for PackageData.
1068 Neither taxes or fees given, but "all inclusive" not set either. Properties without "all inclusive" set must specify taxes and/or fees. The value of taxes and fees may be 0, but they must be given. For properties with known non-zero taxes/fees, include those details For properties with unknown taxes and fees, do not report them, but set "all inclusive". For properties with known, but zero, taxes and fees, report them as 0 and do not set "all inclusive".
1069 There were $0 hotel-itineraries ($1 hotels) missing from the response. Missing hotels: $2 A Query message requests a combination of properties and itineraries. Not all the requested items were returned in the Transaction. Ensure Transactions contain all requested items in the Query.
1070 Can not parse string in RoomUpgradeIncluded, NightlyValue, or OnPropertyCredit: $0 Unable to parse the given text as a float value. Correct the formatting.
1071 Can not parse number of miles in MilesIncluded: $0 Unable to parse the given text as an integer value. Correct the formatting.
1072 $0: Occupancy in RoomBundle was $1 for a room with RoomID $2 and Capacity $3. Occupancy in RoomBundle cannot be larger then the capacity of the room. If the room has capacity of 1, explicitly set Occupancy in RoomBundle to 1. If the room has larger capacity, make sure that the Occupancy in RoomBundle is not larger than that capacity.
1073 $0: No valid RoomBundles specified. Rate set to unavailable. All RoomBundles submitted for the itinerary are invalid and have been rejected. Ensure RoomBundles contain valid data. Specific errors will have been reported separately.
1074 $0: Found hotel price when all RoomBundles are for rooms with capacity 1. Hotel price is for double-occupancy and cannot be specified when all RoomBundles submitted for the itinerary are of capacity 1. Set hotel price to -1 (unavailable) for Results where all available bundles are for rooms with capacity 1.
2001 Unexpected first element $0, expected Bids. The 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. Correct either the file schema or path as appropriate.
Code Message Description Action
2002 Cannot parse $0 as a float for BidRate The text value for BidRate was not parseable as a float. Correct the format.
2003 Cannot parse $0 as a float for DailySpendingCap The text value for DailySpendingCap was not parseable as a float. Correct the format.
2004 Invalid currency string: $0 The 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.
2005 Unexpected attribute of BidRate, $0, is neither type nor currency. An unexpected attribute was given. The message shows the known attribute values. Include only the valid attributes.
2006 Unexpected attribute of DailySpendingCap, $0, is not currency. An unexpected attribute was given. The message shows the known attribute values. Include only the valid attributes.
2007 Attribute $0 given for attributeless element $1 An attribute was given for an element that has no attributes. Do not encode attributes for the given element.
2009 Unknown bid type attribute: $0. Valid types: $1. "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. Ensure the correct data is given for the bid type.
2010 Invalid site string: $0 The site string is not valid. See the Help Center for allowed values. Choose from one of the allowed values.
2011 Invalid country string: $0 The country string is not a recognized country. Choose from one of the allowed values.
2012 Invalid device type string: $0 $1 The device type string may only be mobile. All other types are part of the base bid. Do not specify device type other than mobile.
2013 Invalid min_stay_nights: $0 $1 The MinStayNights text could not parsed as an integer, was negative or the MinStayNights had already been specified. Fix the formatting to comply with all the rules.
2014 Invalid multiplier: $0 The multiplier value could not be parsed as a float. Fix the formatting.
2015 BidMultiplier(s) over or under specified. Must have exactly one constraint per multiplier. $0 A bid multiple must contain exactly one constraint, chosen from: site, user country, length of stay, device type, check-in day of week, and advance booking window. Further, the multiplier value must be between 0.0 and 10.0. Fix the BidMultiplier to comply with the rules.
2016 Bid type 'default' is no longer supported. $0 A bid type of "default" may not be used on or after July 23, 2014. Change any "default" bids to be "fixed" or "percentage" bids.
2017 XML parsing failure. The XML could not be parsed. Correct the XML such that it passes XML lint or equivalent, including the schema.
2018 Unable to parse timestamp attribute The timestamp attribute could not be parsed. It will use the time the file was uploaded.
2019 Multiplier out of range: $0 $1 The bid multiplier value is out of range. Should be between 0.0 and 10.0. (0.5 and 2.0 for date type multipliers.) Fix the bid multiplier value to one that is valid.
2020 Multiple multipliers specified on the same type: $0=$1 $2 Among 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 there aren't duplicate.
2021 Invalid advance booking window min days: $0 $1 The MinDays text could not be parsed as an integer, was negative, was larger than 330, or the MinDays had already been specififed. Fix the formatting to comply with all the rules.
2022 Invalid day of week string: $0 The DayOfWeek text could not be recognized. Fix the formatting to comply with all the rules.
2023 Too many advance booking window multipliers specified. $0 Too many advance booking window multipliers are specified. We only support up to 10 advance booking window multipliers on the same properties. Fix the formatting to comply with all the rules.
2024 Cannot parse $0 as a positive float for MaximumBidCap. The text value for MaximumBidCap could not be parsed as a positive float value. Correct the format.
2025 Unexpected attribute of MaximumBidCap, $0, is not currency. An unexpected attribute was given. The message shows the known attribute values. Include only the valid attributes.
2026 Unexpected attribute of MaximumBidCap, $0, is not currency. The 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.
2028 Invalid Property type: $0, is not hotel, group, or account_default. The 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.
2029 Unexpected attribute of Property, $0, is not type. An unexpected attribute was given. The message shows the known attribute values. Include only the valid attributes.
2030 Missing property hotel name. A Property with type "hotel" is missing a hotel name. Include a hotel name.
2031 Missing property group name. A Property with type "group" is missing a group name. Include a group name.
2032 Unexpected value for property account_default: $0 (should be empty). A Property with type "account_default" specified a value when there shouldn't be one. Don't include a value for type account_default.
2033 No valid properties specified. None of the Properties specified were valid. Ensure that at least one valid Property is specified.
2034 Rate not specified or out of range for a percentage bid. A "percentage" bid was missing rate, or rate is outside of the range of 0.0 - 100.0.
2035 Fixed bid missing rate, missing currency, or rate < 0. A "fixed" bid was missing rate, missing currency, or rate was < 0.0.
2036 Client bid contains deprecated client field. Client bid contains deprecated client field.
2037 Client bid contains deprecated specificity field. Client bid contains deprecated specificity field.
2038 Client bid must have a hotel_bid and not have an effective_hotel_bid. Client bid must have a hotel_bid and not have an effective_hotel_bid.
2039 Invalid bidding group. Invalid bidding group.
2040 Missing account information for bids upload. Missing account information for bids upload.
2041 No bids to process. No bids to process.
2042 Bid has no targets. Bid has no targets.
2043 Cannot set a bid strategy on a hotel. $0 Cannot set a bid strategy on a hotel.
2044 Cannot set a CPC type while setting a non-cleared, non-autopilot or non-enhanced CPC bid strategy. Cannot set a CPC type while setting a non-cleared bid strategy.
2045 Cannot set a bid strategy for a partner not enabled for commission bidding. Cannot set a bid strategy for a partner not enabled for commission bidding.
2046 Bid strategy updates can only be applied to partner or group level bids. Bid strategy updates can only be applied to partner or group level bids.
2048 Bid missing rate. $0 Bid missing rate.
2049 Bidding group must have a non-empty group name. Bidding group must have a non-empty group name.
2050 Hotel bids cannot be set while a group commission bid is active. Hotel bids cannot be set while a group commission bid is active.
2051 Hotel bids cannot be set while a subaccount commission bid is active. Hotel bids cannot be set while a subaccount commission bid is active.
Code Message Description Action
2052 No bid type or strategy specified. No bid type or strategy specified.
2053 Invalid subaccount_id $0 for partner '$1'. Invalid subaccount_id
2054 Lookup of root subaccount for partner '$0' failed. Lookup of root subaccount failed.
2055 The autopilot (max-clicks) bid strategy only works with CPC type billing The autopilot (max-clicks) bid strategy only works with CPC type billing
2056 Cannot write a bid strategy that is disabled for this account. This bid strategy is not enabled for your account. If this bid strategy should be enabled for this partner, enable the bid strategy flag in the PartnerConfiguration.
2057 Internal error setting bid strategy. This is an internal error. Report this error message to engineering.
2058 Minimum conversions per week of $0 not met. The group does not meet the minimum conversions per week. Verify conversion tracking is enabled and/or encourage the partner to select a better performing group of hotels.
2059 Minimum ROAS of $0 not met. The group does not meet the minimum ROAS criteria. Verify conversion tracking is enabled and/or encourage the partner select a better performing group of hotels.
2060 Cannot set commission as account default bid. Deny subaccount level commission bidding.
2061 Cannot set bid because strategy is disabled completely for: $0 Prevent partner sets new bid if bid strategy is disabled.
2062 Cannot set bid because conversion tracking is missing for: $0 Prevent partner sets new bid if conversion tracking and direct booking are missing.
2063 Cannot set bid because conversions are missing for: $0 Prevent partner sets new bid if conversions are missing for this partner.
2064 Cannot set bid because the minimum ratio of base or total price in past 7 days conversions does not meet criterion: $0 for: $1 Prevent partner sets new bid if minimum ratio of base or total price does not meet.
2065 Cannot set bid because the minimum ratio of currency in past 7 days conversions does not meet criterion: $0 for $1 Prevent partner sets new bid if minimum ratio of currency does not meet.
2066 Cannot set bid because the minimum number of hotels in conversions does not meet criterion: $0 for $1 Prevent partner sets new bid if minimum hotels does not meet.
2067 Cannot set bid because the minimum number of conversions per week does not meet criterion: $0 for $1 Prevent partner sets new bid if minimum number of conversions per week does not meet.
2068 Cannot set roas because the minimum roas value in conversions does not meet criterion: $0 for: $1 Prevent partner sets new bid if minimum roas does not meet.
2069 Bid strategy is not supported for: $0 Prevent partner sets new bid if bid strategy is not suported.
2070 Cannot set TargetROAS bids. The value should be in range $0% to $1% Prevent TargetROAS partner sets bids percent out of range.
2071 Cannot set commission bids. The value should be in range $0% to $1% Prevent commission partner sets bids percent out of range.
2072 Invalid date type string: $0 The date type string may only be 'default'. All other types are part of the base bid. Do not specify date type other than 'default'.
2073 Invalid DailySpendingCap: missing required revenue_cap. Invalid DailySpendingCap: missing required revenue_cap.
2074 Invalid DailySpendingCap: missing required currency. Invalid DailySpendingCap: missing required currency.
2075 Invalid MaximumBidCap: missing required maximum_bid. Invalid MaximumBidCap: missing required maximum_bid.
2076 Invalid MaximumBidCap: missing required currency. Invalid MaximumBidCap: missing required currency.
2077 Internal error setting bid. This is an internal error. Report this error message to engineering.
2078 Invalid checkin_days_of_week bitset: $0. $1 This is an internal error. Report this error message to engineering.
2081 Only the campaign default bid may be changed in this request
2082 Bid strategy does not match the campaign strategy
2083 Multiplier type $0 is incompatible with this bid. $1 Multiplier types can be limited by the target (account-default, group, or hotel) of the bid.
2084 Hotel- or group-level bids cannot be set for this bid strategy.
2085 Invalid bid strategy for campaign default.
2086 Campaign bid cannot be cleared.
2087 Enhanced CPC can only be set on the campaign default bid.
2088 CPA bid strategy can only be used in a campaign.
2089 Cannot set CPA bids. The value should be in range $0% to $1% Prevent CPA partner sets bids percent out of range.
2090 Invalid user list id: $0 $1 The audience user list id is not approved for use in a bid multiplier Contact your TAM if you need additional support
3001 Expected first element of Hint, got $0 The 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. Correct either the file schema or path as appropriate.
Code Message Description Action
3002 Invalid FirstDate: $0 The FirstDate text was not parseable as a date. It should be YYYY-MM-DD. Correct the format.
3003 Invalid LastDate: $0 The LastDate text was not parseable as a date. It should be YYYY-MM-DD. Correct the format.
3004 Invalid CheckInDate: $0 The CheckInDate text was not parseable as a date. It should be YYYY-MM-DD. Correct the format.
3005 Invalid LengthOfStay: $0 The text value for LengthOfStay was not parseable as an integer. Correct the format.
3006 Item with Stay missing required element(s), skipping: CheckInDate: $0, LengthOfStay: $1 The Item/Stay was missing either the CheckInDate or a valid length of stay. The message shows which ones are missing. Add the necessary elements.
3007 Item with StaysIncludingRange missing FirstDate. The Item/StaysIncludingRange was missing the required FirstDate. Add the necessary elements.
3008 Item missing required element(s), skipping: FirstDate: $0 LastDate: $1. The Item was missing at least one of the 2 required elements. The message shows which ones are missing. Add the necessary elements.
3009 LengthOfStay too long: $0 Max: $1. Skipping Item: Property: $2 CheckInDate: $3 LengthOfStay: $4 Google'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 30 days. Do not send itineraries with length of stay > 30 days, or correct the value.
3010 CheckInDate $0 before yesterday $1. Skipping Item: Property: $2 CheckInDate: $3 LengthOfStay: $4 We 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. Do not send itineraries with check-in days in the past.
3012 FirstDate $0 is after LastDate $1. When giving a FirstDate and LastDate, the LastDate must be greater than or equal to the FirstDate. Adjust the FirstDate and LastDate as appropriate.
3013 FirstDate $0 is more than $1 days out. Google will not store an itinerary with a check-in date more than 330 days in the future. Do not send itineraries too far in advance.
3014 LastDate $0 is more than $1 days out. Google will adjust any LastDate to be no more than 330 days in advance. Do not send itineraries too far in advance.
3015 Error in POST: $0 An 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.
3016 Unable to find a Google Hotel ID for partner $0, partner hotel id $1. Google 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. In the Hotel Ads Center please check the Tools -> Hotel List -> Matching Report page for additional information regarding a specific property ID. Contact your TAM if you need additional support
3017 LastDate is too early. The LastDate must be today or later. Do not send hints for ranges that have passed out of date.
3018 Item with Stay missing valid partner hotel IDs, skipping. None of the provided hotel ids (if any) could be translated to Google IDs. Ensure the IDs are valid and match those in the hotel feed.
3019 Item with StaysIncludingRange missing valid hotel ids, skipping. Item with StaysIncludingRange missing valid hotel ids, skipping.
3020 Item missing valid hotel ids, skipping. There were no provided hotel ids in the Item. Ensure that every Item contains at least one hotel id. Do not send ones without any hotel ids.
3021 XML parsing failure. The XML could not be parsed. Correct the XML such that it passes XML lint or equivalent, including the schema.
3022 Error from POST: $0 An 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.
4001> Partner $0 is not enabled for storing of room data. Please contact your TAM. Storing 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. Contact your TAM to activate storage.
Code Message Description Action
4002 Unable to parse time stamp: $0 The 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. Correct the timestamp formatting.
4003 Unexpected first element $0, expected HotelInfoFeed. The XML root element was incorrect for a file pushed on this path. Correct either the first element or the path as appropriate.
4004 Will not use occupancy/capacity $0, which is over the limit $1 The 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. Correct 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.
4005 Unable to interpret $0 as a number for occupancy or capacity. Unparseable number provided. Fix the formatting.
4006 Unable to interpret $0 as a boolean. Unparseable boolean provided. Accepted values are: 0, 1, true, false. Fix the formatting.
4007 Will not use $0 refund days, which is greater than limit $1 Google sets a limit on maximum refundable days, mostly to avoid incorrect data. Correct the value, if possible. If the actual value is above the limit, code this room as non-refundable.
4008 Unable to understand $0 as a number for refundable days. Unparseable number provided. Fix the formatting.
4009 Unable to understand $0 as HH:MM. Unparseable time provided. Fix the formatting.
4010 Cannot store data for partner $0, property $1; there is no matching Google hotel id. Google 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. Ensure all necessary information for matching is provided in the hotel feed. Contact your TAM to investigate specific IDs.
4011 Unable to parse as a number: $0 for Baserate. Unparseable number provided. Fix the formatting.
4012 Invalid boolean value for all_inclusive: $0 Unparseable number provided. Fix the formatting.
4013 Invalid currency: $0 The currency code given was not one Google recognizes. Provide a valid currency code.
4014 Can not parse tax and fees string: $0 Unparseable number provided. Fix the formatting.
4015 Unrecognized payment type: $0 The accepted values are: web, hotel and deposit. Provide an accepted value.
4016 Internal error: Unable to finalize with empty partner: $0 An internal error has occurred. Retry the transmission a limited number times. Failing that, contact your TAM.
4017 Could not find google hotel id for partner hotel id: $0, partner $1, id $2 Google 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. Ensure all necessary information for matching is provided in the hotel feed. Contact your TAM to investigate specific IDs.
4018 Empty room_id string in room_data: $0 In order to be accessed from a RoomBundle, a RoomData must have a RoomID. This RoomData was provided without a RoomID. Ensure all RoomData have a RoomID.
4019 Internal error: Unable to finalize without context: $0 An internal error has occurred. This could also be caused by unusual XML structure. Retry the transmission a limited number times. Failing that, contact your TAM.
4020 XML parsing failure. The XML could not be parsed. Correct the XML such that it passes XML lint or equivalent, including the schema.
5001 QueryControl did not evaluate. One or more Items lacked a Property id: $0 One or more of the Item elements in the QueryControl was missing the required Property element. Ensure all Items contain a Property. Validate against the schema.
Code Message Description Action
5002 Unexpected first tag: $0 The 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. Correct either the file schema or path as appropriate.
5003 Found unexpected element: $0 inside $1 An unknown XML element was seen in the response. Validate against the schema.
5006 Unexpected attributes in query control XML: $0 XML attributes were found in the response. The QueryControl message does not use attributes. Remove all attributes. Validate against the schema.
5007 Could not parse max advance purchase days text: $0 The text for MaxAdvancePurchase could not be parsed into an integer value. Check the text value of the MaxAdvancePurchase elements. Validate against the schema.
5008 Could not parse length of stay text: $0 The text for MaxLengthOfStay could not be parsed into an integer value. Check the text value of the MaxLengthOfStay elements. Validate against the schema.
5009 Internal error: Could not parse existing QueryControl message Before accepting a new QueryControl message, the existing message is compared for size. This error indicates an internal error in reading the existing message. Contact your TAM to help clear the error.
5011 Internal Error: Could not find google hotel id for partner hotel id: $0 found in prior QueryControl and not in new QueryControl. When 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. There is no user action required.
5012 Internal error: Unable to parse task data: $0 An internal error occurred. It is possible that a QueryControl transaction was not made on schedule. Contact your TAM.
5013 Internal error: Unsupported task type: $0 An internal error occurred. It is possible that a QueryControl transaction was not made on schedule. Contact your TAM.
5014 Error in POST: $0 An error occurred in fetching the QueryControl response from the partner. Look at internal error logs. If IP addresses have changed, they must be communicated to your TAM.
5016 given with empty text. The text for the MultipleItineraries was not given in the response. Ensure a valid MultipleItineraries text value is given.
5017 Unknown value for : $0 The text for the MultipleItineraries was not one of the allowed values. Ensure a valid MultipleItineraries text value is given.
5018 Will not store QueryControl for id $0, property is either not matched to a Google ID or is overclustered and is not the primary partner id. Google has multiple partner IDs for a single Google ID. We pick one of those as primary. We will not store the query control for the others. If the partner ID is correct, contact your TAM to address any issues with the Hotels Feed.
5019 XML Parsing error. The XML could not be parsed. Correct the XML such that it passes XML lint or equivalent, including the schema.
5020 Could not parse state text: $0 Could not parse state text
5021 $0 Partner uploaded a query control that specified itinerary limits that were either missing one of MaxAdvancedPurchase or MaxLengthOfStay, or specified illegal values for these fields. Have the partner correct the query control that they are sending.
5022 Will not store new empty QueryControl The QueryControl provided is empty. Please provide a QueryControl with the appropriate required fields.
5023 Found unexpected text inside a $0 element: $1 Text was seen within the element, and it should not be present. Remove any excess text within the element.
6001 Internal error: Bad status code: $0 from client IP $1, upload_id: $2 An internal error has occurred. Retry the transmission a limited number times. Failing that, contact your TAM.
Code Message Description Action
6002 Internal error: $0 not single post protocol. The 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. Ensure your transmission uploads the entire file in a single POST.
6003 Internal error: No file name extracted from: $0 An internal error has occurred. Retry the transmission a limited number times. Failing that, contact your TAM.
6004 Internal error: Client address $0 is not recognized or permitted. An internal error has occurred. Retry the transmission a limited number times. Failing that, contact your TAM.
6005 Upload path not recognized: $0 The upload path did not match any of the accepted paths. Correct the upload path. The paths are documented on the developer site.
6006 Partner $0 not allowed from IP $1$2 For 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. Ensure 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.
6007 Could not extract OTA information from OTA message. This indicates that the message was malformed and not in the expected OTA XML format. Ensure the file passes xmllint or equivalent XML validity checker.
6008 No partner tag in file, and no partner with this IP: $0 The uploaded file did not contain a partner attribute, and the partner could not be deduced from the IP address. Add the partner attribute, check your sending IP address. Contact your TAM to change your list of IP addresses.
6009 Do not recognize the partner: $0 The partner name provided in the partner attribute is not a known partner. Check the spelling of the transmitted partner name. Contact your TAM to your exact partner name.
6010 Internal error: Failed to create queue file to add task to task master for partner: $0, filename: $1 An internal error occurred after accepting your job. Retry the transmission a limited number times. Failing that, contact your TAM.
6011 Internal error: Failed to rename: $0 to: $1 status: $2 Request: $3 An internal error occurred after accepting your job. Retry the transmission a limited number times. Failing that, contact your TAM.
6012 Internal error: Failed to create directory for $0: $1 An internal error occurred after accepting your job. Retry the transmission a limited number times. Failing that, contact your TAM.
6013 Parse error in uploaded XML$0 Before acceptance, the file is parsed by a generic XML parser. The parsing failed, so the file is not well formed XML. Ensure the file passes xmllint or equivalent XML validity checker.
6014 No partner tag in file, and multiple partners with this IP: $0 A 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. Provide a partner tag. If the IP address is not supposed to be by any other partner, contact your TAM to investigate.
6015 Transaction PUSH not authorized for partner: $0 A Transaction file was pushed for a partner configured for pull or hint modes. Contact your TAM to change your transmission mode.
6016 Internal error: Parse file not found, and no partner with this IP: $0 An internal error occurred after accepting your job. Retry the transmission a limited number times. Failing that, contact your TAM.
6017 Internal error: Parse file not found, and multiple partners with this IP: $0 An internal error occurred after accepting your job. Retry the transmission a limited number times. Failing that, contact your TAM.
6018 Partner not active: $0 The file was not processed since the partner is not active. Contact your TAM to activate your feed.
6019 No subaccount_id for partner: $0 Check that your partner configuration has not had the alkali_account_id field deleted. Retry the transmission a limited number of times. Failing that, contact your TAM.
6020 Partner mismatch. request_subaccount_id: $0 with partner: $1, but file has partner: $2, with subaccount_id: $3 Partner name in uploaded file does not match that for the request. Verify partner name in feed.
6021 No subaccount_id for ip partner: $0 Check that your partner configuration has not had the alkali_account_id field deleted. Retry the transmission a limited number times. Failing that, contact your TAM.
6022 Internal error: Client address $0 is not recognized or permitted. An internal error has occurred. Retry the transmission a limited number times. Failing that, contact your TAM.
6023 Rejected request from Crimea: IP=$0, Request: $1 IP of request is from a prohibited region. Retry the transmission from an allowed region
6024 Rejected request for gaia_id: $0 for subaccount_id: $1, Request: $2 GAIA authorization of subaccount uploads not yet active. Retry without GAIA login, or use a non-subaccount upload request.
6025 Rejected request for IP=$0 for subaccount_id: $1 without GAIA, no partner for subaccount_id Request: $2 No partner found for requested subaccount_id. Verify subaccount_id in request.
6026 Rejected request for IP=$0 for subaccount_id: $1 without GAIA, IP not valid for partner: $2 Request: $3 IP is not whitelisted for partner. Retry from valid location or have your TAM update your partner configuration.
6027 No partner attribute in file, but partner $0 could be inferred from IP address. 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.
6028 Submitting bids via XML is no longer supported. Submitting bids via XML is no longer supported. Use Hotel Ads Bids API v2.0 or later (https://developers.google.com/hotels/hotel-ads/dev-guide/submitting-bids).
7001 Error from POST: $0 There was an error during POST Check your logs; ensure Google's IP address is correctly whitelisted. Work with your TAM to verify the OTA connection settings.
Code Message Description Action
7002 Error getting partner configuration for $0 There was an error getting the partner configuration Please contact your TAM for them to check that the partner configuration exists for you.
7003 Error getting OTA Pull configuration for $0 There was an error getting the partner configuration Please contact your TAM for them to check check that the ota_xml_pull_configuration field is configured in the protocol configuration.
7004 Error parsing XML message We were unable to parse the XML message as it was malformed. Run xmllint to validate your XML.
7005 Could not determine a hotel id for RoomStay[$0] The RoomStay element with the given index did not have a property id set (and no global property was defined in the message). Please check the property ID.
7006 Cannot find Google hotel id for partner hotel id $0 Our hotels manifest has no corresponding record for the hotel id provided by the partner. Please confirm the hotel has been clustered.
7007 A RoomRate element has multiple currencies in its Rate elements One of the elements in the XML message has elements with different currencies. We don't support this, so we ignore the elements. Please change your XML to use one currency.
7008 Unable to parse price before taxes: $0 Unable to parse the price before taxes from the XML message. The string that we got is given. Please fix the price.
7009 Unable to parse price after taxes: $0 Unable to parse the price after taxes from XML message. The string that we got is given. Please fix the price.
7010 Unable to parse taxes: $0 Unable to parse the taxes from the XML message. The string that we got is given. Please fix the taxes.
7011 Error parsing date range for rate. Effective: $0, Expire: $1 The dates given for a element are not parseable. The Effective and Expire dates are given as they appear in the XML (could be empty) Please fix the date.
7012 Unsupported time unit: $0 We 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. Please change your time unit.
7013 Base price could not be parsed for partner hotel id The 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.
7014 Price with taxes/fees could not be parsed for partner hotel id The 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.
7015 No price could be parsed for partner hotel id We 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.
7016 No currency code could be found for partner hotel id Your 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.
7017 Tpa_Extensions parse has different result for $0 tpa: $1 regular: $2 The 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.
7018 Unable to parse fees: $0 Unable to parse the fees from the XML message. The string that we got is given. Please fix the fees.
7019 XML warning: $0 This is a warning received in the XML response.
7020 XML error: $0 XML error.
7021 XML request did not succeed There was no success element returned There will usually also be 7020 level errors.
8001 Configuration Error: $0 The partner configuration is incorrect. The error message should indicate what is missing. Contact your TAM to fix the partner configuration
Code Message Description Action
8002 Error reading file: $0 There was an error reading the pushed file. Contact your TAM if you frequently see this message
8003 Error parsing XML There was an error parsing the XML file. Check the contents of the associated file to make sure it adheres to our schema.
8004 Error understanding XML message The XML was parseable, but the message included inside is not one we know how to understand. Confirm the XML has correct formatting, reach out to your TAM if you have additional questions.
8005 Unsupported OTA message: $0 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. Ensure you're using one of the supported message types.
8006 Unable to find RestrictionStatus for AvailStatusMessage[$0] We were unable to parse the AvailStatusMessage with the given index, as no RestrictionStatus was present.
8007 Unknown RestrictionStatus for AvailStatusMessage[$0]: $1 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)
8008 Unknown Restriction for AvailStatusMessage[$0]: $1 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)
8009 Failed to parse min LOS for AvailStatusMessage[$0]: $1 We were unable to parse the minimum LOS for the AvailStatusMessage with the given index.
8010 Failed to parse max LOS for AvailStatusMessage[$0]: $1 We were unable to parse the maximum LOS for the AvailStatusMessage with the given index.
8011 Failed to parse min LOS for AvailStatusMessage[$0]: $1 We were unable to parse the minimum LOS for the AvailStatusMessage with the given index.
8012 Failed to parse max LOS for AvailStatusMessage[$0]: $1 We were unable to parse the maximum LOS for the AvailStatusMessage with the given index.
8013 Min LOS ($0) > Max LOS ($1) for AvailStatusMessage[$2] The minimum LOS was greater than the maximum LOS for the AvailStatusMessage with the given index.
8014 Failed to parse status application control in RateAmountMessage[$0] The given RateAmountMessage could not be processed as it was missing the StatusApplicationControl element.
8015 Failed to find AmountBeforeTax in RateAmountMessage[$0]/BaseByGuestAmt[$1] The given XML element was missing the AmountBeforeTax attribute
8016 Unable to find a CurrencyCode for RateAmountMessage[$0]/BaseByGuestAmt [$1], and no default currency is set. Could not find a currency for the given XML element in the RateAmountMessage.
8017 Unable to parse nightly rate for RateAmountMessage[$0]/BaseByGuestAmt[$1]: $2 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.
8018 Could not obtain $0 $1 attribute at property index $2, tax/fee index $3. The Taxes/Fees XML was malformed, and we were unable to pass the given attribute. Make sure you're sending the correct Taxes/Fees XML message (this is Google specific, not OTA)
8019 Could not parse $0 amount attribute at element $1 from: $2 We could not parse the Tax/Fee amount from the XML. Make sure you're sending the correct Taxes/Fees XML message (this is Google specific, not OTA)
8020 Could not parse $0 basis attribute at element $1 from: $2 We were unable to parse the basis attribute for the given Tax/Fee Make sure you're sending the correct Taxes/Fees XML message (this is Google specific, not OTA)
8021 Could not parse $0 period attribute at element $1 from: $2 We were unable to parse the period attribute for the given Tax/Fee Make sure you're sending the correct Taxes/Fees XML message (this is Google specific, not OTA)
8022 Unable to parse a currency (or get one from config) for $0[$1] We were unable to set a currency either from parsing from the XML or from the partner config, for the given Tax/Fee element. Make sure you're sending the correct Taxes/Fees XML message (this is Google specific, not OTA)
8023 Could not parse $0 type attribute at element $1 from: $2 Could not parse the type attribute for the given Tax/Fee Make sure you're sending the correct Taxes/Fees XML message (this is Google specific, not OTA)
8024 Expected one each of RestrictionStatus and LengthOfStay for AvailStatusMessage[$0]. Expected one each of RestrictionStatus and LengthOfStay for AvailStatusMessage
8025 Malformed advanced booking value for AvailStatusMessage[$0]: $1 Malformed advanced booking value for AvailStatusMessage
10001 Expected PointsOfSale, found $0 Expected Point Of Sale
Code Message Description Action
10002 Unexpected element $0 Unexpected Element
10003 Invalid PointOfSale type: $0 Invalid Point of Sale type
10004 Unknown fee type: $0 Unknown fee type
10005 Fee value $0 cannot be parsed as a float Fee value cannot be parsed as a float
10006 Unrecognized attribute $0 Unrecognized attribute
10007 Booking fee is missing for phone POS Booking fee is missing for phone POS
10008 Booking fee currency code is missing Booking fee currency code is missing
10009 Booking fee value is missing Booking fee value is missing
10010 Per-minute fee is missing for phone POS. Per-minute fee is missing for phone POS.
10011 Per-minute fee currency code is missing. Per-minute fee currency code is missing.
10012 Per-minute fee value is missing. Per-minute fee value is missing.
10013 The phone POS $0 doesn't match exactly one approved country The phone POS doesn't match exactly one approved country
10014 Phone number $0 could not be parsed: $1 Phone number could not be parsed
10015 Phone number $0 is invalid for the POS country Phone number is invalid for the POS country
10016 URL is missing in POS $0 URL is missing in POS
10017 The POS $0 is not valid The POS is not valid
10018 Unknown match status: $0 Unknown match status
10019 $0 Language $1 is invalid Language is invalid
10020 Unknown match sitetype: $0 Unknown match sitetype
10021 Unknown match devicetype: $0 Unknown match devicetype
10022 No partner name found for $0. If partner configuration is new you might have struck a race condition. Wait 30 min and update this POS again. No partner name found. If partner configuration is new you might have struck a race condition. Wait 30 min and update this POS again.
10023 Parsing error for partner: $0; error: $1. Parsing error
10024 No valid points of sale found from input for partner $0. No valid points of sale found from input.
10025 Phone number $0 is not in E.164 format. Phone number is not in E.164 format.
9000000 Zero args This is for internal testing. This should not be visible.
9000001 One arg: $0 This is for internal testing. This should not be visible.
Code Message Description Action
9000002 Two args: $0, $1 This is for internal testing. This should not be visible.
9000003 Three args: $0, $1, $2 This is for internal testing. This should not be visible.
9000004 Four args: $0, $1, $2, $3 This is for internal testing. This should not be visible.
9000005 Five args: $0, $1, $2, $3, $4 This is for internal testing. This should not be visible.
9000006 Six args: $0, $1, $2, $3, $4, $5 This is for internal testing. This should not be visible.
9000007 Seven args: $0, $1, $2, $3, $4, $5, $6 This is for internal testing. This should not be visible.
9000008 Eight args: $0, $1, $2, $3, $4, $5, $6, $7 This is for internal testing. This should not be visible.
9000009 Nine args: $0, $1, $2, $3, $4, $5, $6, $7, $8 This is for internal testing. This should not be visible.
9000010 Ten args: $9, $0, $1, $2, $3, $4, $5, $6, $7, $8 This is for internal testing. This should not be visible.

Send feedback about...

Need help? Visit our support page.