The incident was automatically closed because of the following reasons:
The impact of the incident could not be confirmed.
The incident was intermittent or resolved itself.
The incident does not have a resolution because no action or
investigation happened. If it is intermittent, the incident may reopen.
Confirmed
The incident is confirmed and impacting at least one Google Cloud
product. Ongoing status updates will be provided until it is resolved.
Emerging
Google engineers are actively investigating the event to determine the
impact.
FalsePositive
Upon investigation, Google engineers concluded that the incident is not
affecting a Google Cloud product. This state can change if the incident
is reviewed again.
Merged
The incident was merged into a parent incident. All further updates will
be published to the parent only. The parent_event field contains the
name of the parent.
Resolved
The incident is no longer affecting any Google Cloud product, and there
will be no further updates.
[[["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-03-21 UTC."],[[["This documentation details the `Event.Types.DetailedState` enum within the Service Health v1 API, which represents the various states an incident can be in."],["The latest version of the documentation is 1.3.0, and there are also versions 1.2.0, 1.1.0, and 1.0.0 available to access."],["The enum includes states such as `AutoClosed`, `Confirmed`, `Emerging`, `FalsePositive`, `Merged`, `Resolved`, and `Unspecified`, each describing a specific condition of the incident."],["Each state has a corresponding description, outlining the meaning and implications of that particular incident state, like whether Google is actively investigating, whether it is resolved, or whether it is a confirmed issue."]]],[]]