Partial failures, one for each Operation in the request that failed processing. There are three possible combinations of the RPC status: 1. The combination of a successful RPC status and an empty report_errors list indicates a complete success where all Operations in the request are processed successfully. 2. The combination of a successful RPC status and a non-empty report_errors list indicates a partial success where some Operations in the request succeeded. Each Operation that failed processing has a corresponding item in this list. 3. A failed RPC status indicates a general non-deterministic failure. When this happens, it's impossible to know which of the 'Operations' in the request succeeded or failed.
↳ service_config_id
string
The actual config id used to process the request.
↳ service_rollout_id
string
The current service rollout id used to process the request.
getReportErrors
Partial failures, one for each Operation in the request that failed
processing. There are three possible combinations of the RPC status:
The combination of a successful RPC status and an empty report_errors
list indicates a complete success where all Operations in the
request are processed successfully.
The combination of a successful RPC status and a non-empty
report_errors list indicates a partial success where some
Operations in the request succeeded. Each
Operation that failed processing has a corresponding item
in this list.
A failed RPC status indicates a general non-deterministic failure.
When this happens, it's impossible to know which of the
'Operations' in the request succeeded or failed.
Partial failures, one for each Operation in the request that failed
processing. There are three possible combinations of the RPC status:
The combination of a successful RPC status and an empty report_errors
list indicates a complete success where all Operations in the
request are processed successfully.
The combination of a successful RPC status and a non-empty
report_errors list indicates a partial success where some
Operations in the request succeeded. Each
Operation that failed processing has a corresponding item
in this list.
A failed RPC status indicates a general non-deterministic failure.
When this happens, it's impossible to know which of the
'Operations' in the request succeeded or failed.
[[["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,["# Google Cloud Service Control V1 Client - Class ReportResponse (2.0.4)\n\nVersion latestkeyboard_arrow_down\n\n- [2.0.4 (latest)](/php/docs/reference/cloud-service-control/latest/V1.ReportResponse)\n- [2.0.3](/php/docs/reference/cloud-service-control/2.0.3/V1.ReportResponse)\n- [1.4.4](/php/docs/reference/cloud-service-control/1.4.4/V1.ReportResponse)\n- [1.3.0](/php/docs/reference/cloud-service-control/1.3.0/V1.ReportResponse)\n- [1.2.1](/php/docs/reference/cloud-service-control/1.2.1/V1.ReportResponse)\n- [1.1.1](/php/docs/reference/cloud-service-control/1.1.1/V1.ReportResponse)\n- [1.0.6](/php/docs/reference/cloud-service-control/1.0.6/V1.ReportResponse) \nReference documentation and code samples for the Google Cloud Service Control V1 Client class ReportResponse.\n\nResponse message for the Report method.\n\nGenerated from protobuf message `google.api.servicecontrol.v1.ReportResponse`\n\nNamespace\n---------\n\nGoogle \\\\ Cloud \\\\ ServiceControl \\\\ V1\n\nMethods\n-------\n\n### __construct\n\nConstructor.\n\n### getReportErrors\n\nPartial failures, one for each `Operation` in the request that failed\nprocessing. There are three possible combinations of the RPC status:\n\n1. The combination of a successful RPC status and an empty `report_errors`\n list indicates a complete success where all `Operations` in the\n request are processed successfully.\n\n2. The combination of a successful RPC status and a non-empty\n `report_errors` list indicates a partial success where some\n `Operations` in the request succeeded. Each\n `Operation` that failed processing has a corresponding item\n in this list.\n\n3. A failed RPC status indicates a general non-deterministic failure. When this happens, it's impossible to know which of the 'Operations' in the request succeeded or failed.\n\n### setReportErrors\n\nPartial failures, one for each `Operation` in the request that failed\nprocessing. There are three possible combinations of the RPC status:\n\n1. The combination of a successful RPC status and an empty `report_errors`\n list indicates a complete success where all `Operations` in the\n request are processed successfully.\n\n2. The combination of a successful RPC status and a non-empty\n `report_errors` list indicates a partial success where some\n `Operations` in the request succeeded. Each\n `Operation` that failed processing has a corresponding item\n in this list.\n\n3. A failed RPC status indicates a general non-deterministic failure. When this happens, it's impossible to know which of the 'Operations' in the request succeeded or failed.\n\n### getServiceConfigId\n\nThe actual config id used to process the request.\n\n### setServiceConfigId\n\nThe actual config id used to process the request.\n\n### getServiceRolloutId\n\nThe current service rollout id used to process the request.\n\n### setServiceRolloutId\n\nThe current service rollout id used to process the request."]]
