The response to a Health Check probe had the HTTP response header field X-Load-Balancing-Endpoint-Weight, but its content was invalid (i.e., not a non-negative single-precision floating-point number in decimal string representation).
MissingWeight
The response to a Health Check probe did not have the HTTP response header field X-Load-Balancing-Endpoint-Weight.
UnavailableWeight
This is the value when the accompanied health status is either TIMEOUT (i.e.,the Health Check probe was not able to get a response in time) or UNKNOWN. For the latter, it should be typically because there has not been sufficient time to parse and report the weight for a new backend (which is with 0.0.0.0 ip address). However, it can be also due to an outage case for which the health status is explicitly reset to UNKNOWN.
UndefinedWeightError
A value indicating that the enum field is not set.
WeightNone
This is the default value when WeightReportMode is DISABLE, and is also the initial value when WeightReportMode has just updated to ENABLE or DRY_RUN and there has not been sufficient time to parse and report the backend weight.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-08 UTC."],[[["\u003cp\u003eThis page details the \u003ccode\u003eWeightError\u003c/code\u003e enum within the \u003ccode\u003eGoogle.Cloud.Compute.V1\u003c/code\u003e namespace, specifically found in the \u003ccode\u003eGoogle.Cloud.Compute.V1.dll\u003c/code\u003e assembly, and includes documentation for version 1.4.0 and other past versions.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eWeightError\u003c/code\u003e enum has several possible values, including \u003ccode\u003eInvalidWeight\u003c/code\u003e, \u003ccode\u003eMissingWeight\u003c/code\u003e, \u003ccode\u003eUnavailableWeight\u003c/code\u003e, \u003ccode\u003eUndefinedWeightError\u003c/code\u003e, and \u003ccode\u003eWeightNone\u003c/code\u003e, each describing different scenarios related to HTTP response header field \u003ccode\u003eX-Load-Balancing-Endpoint-Weight\u003c/code\u003e in health checks.\u003c/p\u003e\n"],["\u003cp\u003eThe most recent version documented on this page is 3.6.0, which is noted as the latest, but there is documentation available for multiple previous versions as far back as 1.0.0.\u003c/p\u003e\n"],["\u003cp\u003eThe WeightError enum is used to report on any issues associated with the X-Load-Balancing-Endpoint-Weight such as missing headers, invalid values, or if the check timed out.\u003c/p\u003e\n"]]],[],null,[]]
