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

# Replay Failed Deliveries



## OpenAPI

````yaml POST /v1/webhooks/deliveries/replay-failed
openapi: 3.0.3
info:
  title: Dome Platform API
  description: Connect and REST APIs for the Dome agent governance platform.
  version: 2.0.0
servers:
  - url: https://api.domesystems.ai
    description: Production
security: []
tags:
  - name: Agents
  - name: Authorization
  - name: Guards
  - name: Tools
  - name: Tool Catalog
  - name: Models
  - name: Model Pools
  - name: Quotas
  - name: Gateways
  - name: Webhooks
  - name: Audit
  - name: Workspaces
  - name: Access Control
  - name: Tenants
  - name: Platform Keys
  - name: Enrollment
  - name: Platform
  - name: Identity
paths:
  /v1/webhooks/deliveries/replay-failed:
    post:
      tags:
        - Webhooks
      operationId: EventingService_ReplayFailedDeliveries
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/ReplayFailedDeliveriesRequest'
        required: true
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ReplayFailedDeliveriesResponse'
components:
  schemas:
    ReplayFailedDeliveriesRequest:
      type: object
      properties:
        workspace_id:
          type: string
        destination_id:
          type: string
          description: >-
            Optional: restrict recovery to one destination. Empty = every
            destination in
             the workspace.
        since:
          type: string
          description: >-
            Required inclusive lower bound on the original delivery's
            created_at. Must be
             no more than 30 days ago — the body-retention horizon, beyond which the
             canonical bytes no longer exist to re-send.
          format: date-time
        until:
          type: string
          description: Optional inclusive upper bound on created_at; defaults to now.
          format: date-time
        statuses:
          type: array
          items:
            type: string
          description: >-
            Statuses to recover — a subset of {"failed", "expired", "dlq"};
            empty selects
             all three. "canceled" is deliberately excluded: an operator canceled those on
             purpose, so a bulk recovery must never resurrect them.
        max_deliveries:
          type: integer
          description: >-
            Maximum deliveries to recover in one call. Clamped to [1, 500]; 0
            defaults to
             100. Endpoint pacing stays with the delivery worker's per-destination rate
             limiter — this only bounds how much one call enqueues.
          format: int32
      description: >-
        ReplayFailedDeliveriesRequest bulk-recovers terminal deliveries in a
        time
         window — the outage-recovery counterpart to per-delivery ReplayDelivery.

         Each recovered delivery re-sends its retained canonical bytes verbatim under a
         fresh delivery id: that is a NEW webhook message, not a resurrection of the old
         one (the standard-webhooks id changes). Consumers dedupe on Dome-Event-Id, so a
         recovery that overlaps deliveries a consumer already processed is safe.
    ReplayFailedDeliveriesResponse:
      type: object
      properties:
        matched:
          type: integer
          description: |-
            matched is how many recoverable deliveries the filter selected (<=
             max_deliveries). A delivery is skipped from the match when it already has a
             live or succeeded replay child, so re-running the same recovery converges.
          format: int32
        replayed:
          type: integer
          description: replayed is how many were re-enqueued under a fresh delivery id.
          format: int32
        skipped_body_expired:
          type: integer
          description: >-
            skipped_body_expired is how many matched deliveries could not be
            replayed
             because their canonical body had aged out of the ledger since the match.
          format: int32
        failed:
          type: integer
          description: >-
            failed is how many matched deliveries errored during replay
            (transient infra);
             re-running the recovery retries them.
          format: int32
        replay_delivery_ids:
          type: array
          items:
            type: string
          description: |-
            replay_delivery_ids are the new delivery ids minted for the replayed
             deliveries.
      description: >-
        ReplayFailedDeliveriesResponse reports the recovery outcome counters
        plus the
         ids of the freshly minted replay deliveries.

````