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

# Retry a chat-id document

> Retry a failed Deep Reader document by chat id.

`{id}` is the Deep Reader **chat** pk. Failed rows resume (cache kept); this is not a full reprocess. Prefer [Reprocess](/api-reference/documents/reprocess) for the attachment-id surface.


## OpenAPI

````yaml POST /api/v2/documents/{id}/retry/
openapi: 3.1.0
info:
  title: Abacus Docs API
  version: 1.0.0
  description: |
    REST + SSE surface for Abacus Docs on the same host as the web app
    (`https://abacusdocs.com`). Paths are `/api/v2/…`.

    Authenticate with an organisation API key (`sk-abacus-*`) as a Bearer
    token, or an Auth0 access token. Cross-tenant reads return **404**, not
    403. Page-based lists use `?page=` and `?page_size=`.

    Extraction, reprocess, schema tests, and chat turns spend credits.
    See the help centre Credits pages for rates.
  contact:
    name: Abacus Docs
    url: https://abacusdocs.com/contact
servers:
  - url: https://abacusdocs.com
    description: Production (Extract)
security: []
paths:
  /api/v2/documents/{id}/retry/:
    post:
      tags:
        - v2/documents
      summary: Retry document processing
      description: >-
        Re-queues a failed document for processing. Returns 409 if the document
        is not in the `failed` state (already pending, processing, or
        completed).
      operationId: v2_documents_retry_create
      parameters:
        - in: path
          name: id
          schema:
            type: integer
          required: true
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Progress'
          description: ''
        '404':
          description: No response body
        '409':
          description: No response body
      security:
        - extractApiKey: []
        - bearerAuth: []
        - cookieAuth: []
components:
  schemas:
    Progress:
      type: object
      description: >-
        Processing status snapshot for the progress-polling endpoint.


        Serializes ChatAttachment directly (not Chat) because the progress
        endpoint

        queries the attachment by chat pk.
      properties:
        status:
          type: string
        progress:
          type: integer
        stage:
          type: string
        page_count:
          type: integer
          maximum: 2147483647
          minimum: 0
          description: Number of pages in the original document
      required:
        - progress
        - stage
        - status
  securitySchemes:
    extractApiKey:
      type: http
      scheme: bearer
      bearerFormat: API Key
      description: |
        Organisation API key from Settings → API / `/api/keys/`. The secret is
        shown once. Send `Authorization: Bearer sk-abacus-…`. One active key
        per organisation. Ingest (`/api/v2/ingest/*`) refuses API keys — that
        surface is Auth0-only with `ingest:read` / `ingest:write` scopes.
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: >
        Auth0 access token for a signed-in user. Send `Authorization: Bearer
        <token>`.

        The SPA and desktop agent use this. Prefer an organisation API key for

        server-to-server integrations.
    cookieAuth:
      type: apiKey
      in: cookie
      name: sessionid
      description: |
        Django session cookie from a browser login. Present so the web app can
        call `/api/v2` without a header. Do not rely on this for integrations.

````