> ## Documentation Index
> Fetch the complete documentation index at: https://docsv4.mile.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Unresolve alert

> Clears the resolution of an alert (resolver, time and notes) so it is unresolved again. Linked notifications are updated too. Calling it on an unresolved alert changes nothing and still returns `200`.

An alert of another organization returns `404`.

Requires permission `resolve/alert`.



## OpenAPI

````yaml /openapi/public/openapi-monitoring.json delete /alert/{id}/resolve
openapi: 3.0.0
info:
  title: API - Monitoring
  version: 3.0.0
  description: API Documentation - RESTful API for field operations management.
servers:
  - url: https://apiweb.mile.app/api/v3
security:
  - bearerAuth: []
tags:
  - name: Alert
    description: >-
      An alert is an event raised while monitoring field users and vehicles, for
      example entering or leaving a geofence, idling too long, a predicted late
      task, a route deviation or a panic button press. You can list alerts, read
      a daily summary, and mark them resolved. These endpoints are served under
      `/api/v4`.
  - name: Alert Setting
    description: >-
      Alert settings switch each alert type on or off for your organization.
      These endpoints are served under `/api/v4`.
  - name: Geofence
    description: >-
      A geofence is an area drawn on the map, as a polygon or a circle. Alerts
      and automations can react when a field user enters or leaves it, or stays
      inside longer than its dwell time.
  - name: Geofence Group
    description: >-
      Geofence groups organize geofences so you can filter and manage them
      together.
paths:
  /alert/{id}/resolve:
    servers:
      - url: https://apiweb.mile.app/api/v4
    delete:
      tags:
        - Alert
      summary: Unresolve alert
      description: >-
        Clears the resolution of an alert (resolver, time and notes) so it is
        unresolved again. Linked notifications are updated too. Calling it on an
        unresolved alert changes nothing and still returns `200`.


        An alert of another organization returns `404`.


        Requires permission `resolve/alert`.
      operationId: unresolveAlert
      parameters:
        - name: id
          in: path
          required: true
          description: |-
            Unique identifier of the alert, generated by the system.
            **Example:** `66fb0c1d2e3f4a5b6c7d8e9f`
          schema:
            type: string
      responses:
        '200':
          description: Success
          content:
            application/json:
              schema:
                type: object
                properties:
                  status:
                    type: boolean
                    description: Status of response.
                  message:
                    description: Message of API response.
                    type: string
                  data:
                    description: The alert, now unresolved.
                    type: object
                    additionalProperties: true
                example:
                  status: true
                  message: Success
                  data:
                    _id: 66fb0c1d2e3f4a5b6c7d8e9f
                    organizationId: 64d99303be0ad015c461c932
                    assignee: driver@example.com
                    alertCode: geofence.enter
                    alertName: Geofence enter
                    lat: -6.2001
                    lon: 106.8166
                    eventTime: '2026-10-15T02:10:00+00:00'
                    data:
                      geofenceId: 66e0a1b2c3d4e5f6a7b8c9d0
                      geofenceName: Warehouse A
                      geofenceGroup: 66e0a0b1c2d3e4f5a6b7c8d9
                    isResolved: false
                    resolvedTime: null
                    resolvedBy: null
                    resolvedByName: null
                    resolvedNotes: null
                    createdTime: '2026-10-15T02:10:02+00:00'
                    updatedTime: '2026-10-15T03:05:00+00:00'
        '404':
          description: Data not found
          content:
            application/json:
              schema:
                type: object
                properties:
                  status:
                    type: boolean
                    description: Shows if the request was successful.
                  message:
                    type: string
                    description: A short message explaining what went wrong.
                example:
                  status: false
                  message: Data not found
      deprecated: false
      security:
        - bearerAuth: []
components:
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: Use a valid Bearer token to authenticate.

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.