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

# Recover an aborted workflow execution

> Continues a run that a server restart aborted as a new run: nodes that finished are replayed from their recorded output, the rest run again. Needs the file execution log and checkpoint directories. Answers 409 if the run was not aborted, was already resumed or its workflow changed.



## OpenAPI

````yaml /api/openapi.json post /api/executions/{executionId}/recover
openapi: 3.1.0
info:
  title: Yukta REST API
  version: 0.0.1-SNAPSHOT
  description: >-
    Create sessions and workflows, start and steer executions, and read their
    status, logs and results. Pre-beta: paths and schemas may change before
    v0.1.0.
servers:
  - url: http://localhost:8080
    description: Local server (default address)
security:
  - bearerAuth: []
  - apiKeyAuth: []
tags:
  - name: Supervisors API
    description: Supervisors and control planes on the control bus
  - name: Workflow Versions API
    description: List the saved versions and roll back
  - name: Workflow API
    description: Endpoints for starting workflows and listing their executions
  - name: Execution API
    description: Stop, restart and observe workflow executions
  - name: Execution Search API
    description: Find runs across sessions
  - name: Control Bus & Observability API
    description: >-
      Endpoints for control bus operations, node management, and execution
      observability
  - name: Execution Control API
    description: Pause, resume, step and stop nodes
  - name: Session API
    description: Endpoints for session and workflow discovery, configuration management
  - name: Session API
    description: Validate a draft workflow without saving it
  - name: Workers API
    description: Workers connected to the control plane
  - name: Events API
    description: Live feed of execution events
  - name: Workflow Details API
    description: Workflow DAG graph with plugin metadata and per-workflow execution history
  - name: Execution Results API
    description: Follow the result of an execution
  - name: Execution Logs API
    description: Stream execution logs
  - name: Control audit API
    description: Control commands and who sent them
  - name: Plugin API
    description: Endpoints for discovering workflow plugins
paths:
  /api/executions/{executionId}/recover:
    post:
      tags:
        - Execution Control API
      summary: Recover an aborted workflow execution
      description: >-
        Continues a run that a server restart aborted as a new run: nodes that
        finished are replayed from their recorded output, the rest run again.
        Needs the file execution log and checkpoint directories. Answers 409 if
        the run was not aborted, was already resumed or its workflow changed.
      operationId: recoverExecution
      parameters:
        - name: executionId
          in: path
          description: Execution ID
          required: true
          schema:
            type: string
      responses:
        '200':
          description: OK
          content:
            '*/*':
              schema:
                $ref: '#/components/schemas/ApiResponseWorkflowStartResponse'
components:
  schemas:
    ApiResponseWorkflowStartResponse:
      type: object
      description: >-
        Unified API response wrapper for both success and error responses.
        Success responses include data field; error responses include error,
        path, and errors fields.
      properties:
        timestamp:
          type: string
          format: date-time
          description: The time the response was generated
        status:
          type: integer
          format: int32
          description: The HTTP status code
          example: 200
        message:
          type: string
          description: A human-readable message
          example: Operation successful
        data:
          $ref: '#/components/schemas/WorkflowStartResponse'
          description: The response data
        error:
          type: string
          description: The HTTP status error name
          example: Bad Request
        path:
          type: string
          description: The request path
          example: /api/files
        errors:
          type: array
          description: The list of field validation errors
          items:
            $ref: '#/components/schemas/FieldError'
    WorkflowStartResponse:
      type: object
      description: Response object for triggering a workflow
      properties:
        executionId:
          type: string
          description: The unique execution identifier
          example: 550e8400-e29b-41d4-a716-446655440000
    FieldError:
      type: object
      description: Field-specific validation error detail
      properties:
        field:
          type: string
          description: The name of the field that failed validation
          example: sessionId
        message:
          type: string
          description: The validation error message explaining the failure
          example: 'Session not found: ''unknown-session'''
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: >-
        API key sent as `Authorization: Bearer <key>`. Needed only when the
        server has a key configured.
    apiKeyAuth:
      type: apiKey
      in: header
      name: X-API-Key
      description: The same API key sent as `X-API-Key`.

````

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