Reference documentation and code samples for the Compute V1 Client class Status.
TheStatustype defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used bygRPC. EachStatusmessage contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in theAPI Design Guide.
Generated from protobuf messagegoogle.cloud.compute.v1.Status
Namespace
Google \ Cloud \ Compute \ V1
Methods
__construct
Constructor.
Parameters
Name
Description
data
array
Optional. Data for populating the Message object.
↳ code
int
The status code, which should be an enum value of google.rpc.Code.
A list of messages that carry the error details. There is a common set of message types for APIs to use.
↳ message
string
A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the google.rpc.Status.details field, or localized by the client.
getCode
The status code, which should be an enum value of google.rpc.Code.
Returns
Type
Description
int
hasCode
clearCode
setCode
The status code, which should be an enum value of google.rpc.Code.
Parameter
Name
Description
var
int
Returns
Type
Description
$this
getDetails
A list of messages that carry the error details. There is a common set of message types for APIs to use.
A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the google.rpc.Status.details field, or localized by the client.
Returns
Type
Description
string
hasMessage
clearMessage
setMessage
A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the google.rpc.Status.details field, or localized by the client.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 UTC."],[],[],null,["# Compute V1 Client - Class Status (1.35.0)\n\nVersion latestkeyboard_arrow_down\n\n- [1.35.0 (latest)](/php/docs/reference/cloud-compute/latest/V1.Status)\n- [1.34.0](/php/docs/reference/cloud-compute/1.34.0/V1.Status)\n- [1.33.0](/php/docs/reference/cloud-compute/1.33.0/V1.Status)\n- [1.32.0](/php/docs/reference/cloud-compute/1.32.0/V1.Status)\n- [1.31.0](/php/docs/reference/cloud-compute/1.31.0/V1.Status)\n- [1.30.0](/php/docs/reference/cloud-compute/1.30.0/V1.Status)\n- [1.29.0](/php/docs/reference/cloud-compute/1.29.0/V1.Status)\n- [1.28.0](/php/docs/reference/cloud-compute/1.28.0/V1.Status)\n- [1.27.0](/php/docs/reference/cloud-compute/1.27.0/V1.Status)\n- [1.26.0](/php/docs/reference/cloud-compute/1.26.0/V1.Status)\n- [1.25.0](/php/docs/reference/cloud-compute/1.25.0/V1.Status)\n- [1.24.0](/php/docs/reference/cloud-compute/1.24.0/V1.Status)\n- [1.23.0](/php/docs/reference/cloud-compute/1.23.0/V1.Status)\n- [1.22.1](/php/docs/reference/cloud-compute/1.22.1/V1.Status)\n- [1.21.0](/php/docs/reference/cloud-compute/1.21.0/V1.Status)\n- [1.20.0](/php/docs/reference/cloud-compute/1.20.0/V1.Status)\n- [1.19.0](/php/docs/reference/cloud-compute/1.19.0/V1.Status)\n- [1.18.1](/php/docs/reference/cloud-compute/1.18.1/V1.Status)\n- [1.17.0](/php/docs/reference/cloud-compute/1.17.0/V1.Status)\n- [1.16.2](/php/docs/reference/cloud-compute/1.16.2/V1.Status)\n- [1.14.0](/php/docs/reference/cloud-compute/1.14.0/V1.Status)\n- [1.13.0](/php/docs/reference/cloud-compute/1.13.0/V1.Status)\n- [1.12.1](/php/docs/reference/cloud-compute/1.12.1/V1.Status)\n- [1.11.1](/php/docs/reference/cloud-compute/1.11.1/V1.Status)\n- [1.10.1](/php/docs/reference/cloud-compute/1.10.1/V1.Status)\n- [1.9.1](/php/docs/reference/cloud-compute/1.9.1/V1.Status)\n- [1.8.3](/php/docs/reference/cloud-compute/1.8.3/V1.Status)\n- [1.7.1](/php/docs/reference/cloud-compute/1.7.1/V1.Status)\n- [1.6.1](/php/docs/reference/cloud-compute/1.6.1/V1.Status)\n- [1.5.0](/php/docs/reference/cloud-compute/1.5.0/V1.Status) \nReference documentation and code samples for the Compute V1 Client class Status.\n\nThe `Status` type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by [gRPC](https://github.com/grpc). Each `Status` message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the [API Design Guide](https://cloud.google.com/apis/design/errors).\n\nGenerated from protobuf message `google.cloud.compute.v1.Status`\n\nNamespace\n---------\n\nGoogle \\\\ Cloud \\\\ Compute \\\\ V1\n\nMethods\n-------\n\n### __construct\n\nConstructor.\n\n### getCode\n\nThe status code, which should be an enum value of google.rpc.Code.\n\n### hasCode\n\n### clearCode\n\n### setCode\n\nThe status code, which should be an enum value of google.rpc.Code.\n\n### getDetails\n\nA list of messages that carry the error details. There is a common set of message types for APIs to use.\n\n### setDetails\n\nA list of messages that carry the error details. There is a common set of message types for APIs to use.\n\n### getMessage\n\nA developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the google.rpc.Status.details field, or localized by the client.\n\n### hasMessage\n\n### clearMessage\n\n### setMessage\n\nA developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the google.rpc.Status.details field, or localized by the client."]]
