---
title: "UpdateAnomalyAlert"
description: "Triage an anomaly alert"
canonical: "https://pgbeam.com/docs/go-sdk/anomalies/updateAnomalyAlert"
last-updated: "2026-09-14T19:37:21.000Z"
---

# UpdateAnomalyAlert

> Triage an anomaly alert

URL: https://pgbeam.com/docs/go-sdk/anomalies/updateAnomalyAlert

Updates the triage status of an anomaly alert (acknowledge or resolve).

## Usage

## Parameters

Parameter

Type

Required

Description

ctx

`context.Context`

Yes

Request context

projectID

`string`

Yes

Unique project identifier (prefixed, e.g. prj\_xxx).

anomalyID

`string`

Yes

Unique anomaly alert identifier (prefixed, e.g. ano\_xxx).

req

`pgbeam.UpdateAnomalyAlertRequest`

Yes

Request body

req.Status

`string`

Yes

New triage state for the alert.

## Response

`(*pgbeam.AnomalyAlert, error)`: the updated anomaly alert.

## Example

## Errors

Status

Description

400

The request was rejected. `code` is `INVALID_INPUT`, and `errors` names the offending fields when the failure was a validation one.

401

Missing or invalid authentication. `code` is `UNAUTHORIZED`.

403

The caller is authenticated but not allowed to perform this operation. `code` is `FORBIDDEN` when the caller's role is insufficient, and `PLAN_LIMIT_REACHED` when the organization's plan is what stands in the way. The two are answered differently, so branch on the code rather than the status.

404

The resource does not exist, or the caller is not entitled to know that it does. `code` is `NOT_FOUND`.

413

The request body exceeds the 2 MB limit. `code` is `PAYLOAD_TOO_LARGE`.

415

The request body is not JSON, or carries a body without declaring a Content-Type. `code` is `UNSUPPORTED_MEDIA_TYPE`.

500

The request failed for a reason on our side. `code` is `INTERNAL_ERROR`. Quote `request_id` when reporting it.