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

# Reprocess a failed order (admin)

> Reprocesses a FAILED judicial order: claims it back to PENDING and audits the transition. The subject is re-dispatched immediately (dispatched:true) ONLY when execution is enabled AND the order carries a subject hash; otherwise the order is transitioned to PENDING and queued for the next execution cycle (dispatched:false). The institution is derived from the validated request identity, never the path. The order id comes from the path.



## OpenAPI

````yaml en/openapi/v3-current/sisbajud.yaml post /v1/admin/orders/{id}/reprocess
openapi: 3.0.3
info:
  title: Lerian SISBAJUD API
  description: >-
    API for Lerian SISBAJUD — the participant-side rail that integrates the
    institution with Banco Central do Brasil's SISBAJUD (Sistema de Busca de
    Ativos do Poder Judiciário) system for judicial asset blocking and
    unblocking. It covers judicial-order administration, remittance and return
    file management, reconciliation, SLA monitoring, LGPD data-subject requests,
    and per-institution configuration and connector credentials.
  version: v1.0.0
servers:
  - url: https://sisbajud.sandbox.lerian.net
security: []
tags:
  - name: Admin
    description: >-
      Administrative operations over judicial orders: listing and detail,
      failed-order reprocessing, remittance and return file access,
      reconciliation runs and status, SLA-risk monitoring, processing
      statistics, audit-trail verification, cross-organization subject
      summaries, and LGPD data-subject requests and justifications.
  - name: Institution
    description: >-
      Per-institution configuration and connector credentials: configuration
      upsert with tokenization-keyset provisioning, safe configuration read, and
      outbound connector credential registration and rotation.
paths:
  /v1/admin/orders/{id}/reprocess:
    post:
      tags:
        - Admin
      summary: Reprocess a failed order (admin)
      description: >-
        Reprocesses a FAILED judicial order: claims it back to PENDING and
        audits the transition. The subject is re-dispatched immediately
        (dispatched:true) ONLY when execution is enabled AND the order carries a
        subject hash; otherwise the order is transitioned to PENDING and queued
        for the next execution cycle (dispatched:false). The institution is
        derived from the validated request identity, never the path. The order
        id comes from the path.
      parameters:
        - description: Judicial order id (UUID)
          in: path
          name: id
          required: true
          schema:
            type: string
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/http.ReprocessResponse'
        '400':
          description: Bad Request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/http.AdminErrorResponse'
        '403':
          description: Forbidden
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/http.AdminErrorResponse'
        '404':
          description: Not Found
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/http.AdminErrorResponse'
        '422':
          description: Unprocessable Entity
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/http.AdminErrorResponse'
        '500':
          description: Internal Server Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/http.AdminErrorResponse'
        '503':
          description: Service Unavailable
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/http.AdminErrorResponse'
      security:
        - BearerAuth: []
components:
  schemas:
    http.ReprocessResponse:
      properties:
        dispatched:
          type: boolean
        newStatus:
          type: string
        orderId:
          type: string
      type: object
    http.AdminErrorResponse:
      properties:
        code:
          type: string
        details:
          additionalProperties: {}
          type: object
        message:
          type: string
        title:
          type: string
      type: object
  securitySchemes:
    BearerAuth:
      description: 'Bearer token authentication (format: "Bearer {token}")'
      in: header
      name: Authorization
      type: apiKey

````