Reset Alert

### Reset a triggered or failed alert and resume watching. **Available to:** All authenticated users **Environments:** Demo, Live **[Rate Limit](/api/authentication#request-rate-limits-and-time-penalties):** No endpoint-specific limit Re-arms the alert identified by `alertId`. The alert must belong to the calling user. Use this after an alert has triggered, expired, or failed to keep the same alert and wait for its condition to be met again. The server stops watching, re-parses the alert's existing `expression`, sets `status` back to `Active`, clears the `triggeredCounter` and any `failure`, and resumes watching. The alert's `expression`, `validUntil`, `triggerLimits`, and `message` are preserved — to change those values, use [`modifyAlert`](/api/rest-api-endpoints/alerts/modify-alert) instead. The request body contains a single required field, `alertId`, from [`createAlert`](/api/rest-api-endpoints/alerts/create-alert) or [`alertItem`](/api/rest-api-endpoints/alerts/alert-item). The response returns the reactivated `alert`. **Common Failure Scenarios** - `alertId` does not exist or is not owned by the calling user. - The stored `expression` can no longer be parsed (for example, after a configuration change), so the alert cannot be reactivated. **Error Messages** | `errorText` | Trigger | |-------------|---------| | Non-empty `errorText` | The request failed; the field describes the reason (most commonly a stored `expression` that could not be parsed). |