> ## 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.

# Get the tree of runs below an execution

> The execution and every run it started as a sub-workflow, at any depth, oldest first, each with its parentExecutionId and status



## OpenAPI

````yaml /api/openapi.json get /api/executions/{executionId}/tree
openapi: 3.1.0
info:
  description: >-
    Create sessions and workflows, start and steer executions, and read their
    status, logs and results. Alpha: paths and schemas may change before v0.1.0.
  title: Yukta REST API
  version: 0.1.0-alpha.3
servers: []
security:
  - bearerAuth: []
  - apiKeyAuth: []
tags:
  - description: Supervisors and control planes on the control bus
    name: Supervisors API
  - description: List the saved versions and roll back
    name: Workflow Versions API
  - description: Endpoints for starting workflows and listing their executions
    name: Workflow API
  - description: Edition, licence and features of this build
    name: Edition API
  - description: Stop, restart and observe workflow executions
    name: Execution API
  - description: Find runs across sessions
    name: Execution Search API
  - description: >-
      Endpoints for control bus operations, node management, and execution
      observability
    name: Control Bus & Observability API
  - description: Who is calling and what the key may do
    name: Session API
  - description: Read part of the output of a node
    name: Node Output API
  - description: Pause, resume, step and stop nodes
    name: Execution Control API
  - description: Endpoints for session and workflow discovery, configuration management
    name: Session API
  - description: Validate a draft workflow without saving it
    name: Session API
  - description: Workers connected to the control plane
    name: Workers API
  - description: Live feed of execution events
    name: Events API
  - description: Workflow DAG graph with plugin metadata and per-workflow execution history
    name: Workflow Details API
  - description: Follow the result of an execution
    name: Execution Results API
  - description: Stream execution logs
    name: Execution Logs API
  - description: Control commands and who sent them
    name: Control audit API
  - description: Example sessions to start from
    name: Templates API
  - description: Signed inbound calls that start a workflow
    name: Webhook API
  - description: Check a working directory before creating a session
    name: Session API
  - description: Endpoints for discovering workflow plugins
    name: Plugin API
paths:
  /api/executions/{executionId}/tree:
    get:
      tags:
        - Execution API
      summary: Get the tree of runs below an execution
      description: >-
        The execution and every run it started as a sub-workflow, at any depth,
        oldest first, each with its parentExecutionId and status
      operationId: getTree
      parameters:
        - description: Execution ID
          in: path
          name: executionId
          required: true
          schema:
            type: string
      responses:
        '200':
          content:
            '*/*':
              schema:
                $ref: '#/components/schemas/ApiResponseListWorkflowExecutionSummary'
          description: OK
components:
  schemas:
    ApiResponseListWorkflowExecutionSummary:
      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:
        data:
          description: The response data
          items:
            $ref: '#/components/schemas/WorkflowExecutionSummary'
          type: array
        error:
          description: The HTTP status error name
          example: Bad Request
          type: string
        errors:
          description: The list of field validation errors
          items:
            $ref: '#/components/schemas/FieldError'
          type: array
        message:
          description: A human-readable message
          example: Operation successful
          type: string
        path:
          description: The request path
          example: /api/files
          type: string
        status:
          description: The HTTP status code
          example: 200
          format: int32
          type: integer
        timestamp:
          description: The time the response was generated
          format: date-time
          type: string
      type: object
    WorkflowExecutionSummary:
      description: Summary of a workflow execution
      properties:
        endTime:
          description: The end time of the execution, with the server's UTC offset
          format: date-time
          type:
            - string
            - 'null'
        executionId:
          description: The unique execution identifier
          type: string
        nodes:
          $ref: '#/components/schemas/Nodes'
          description: How far the run got through its nodes
          type: 'null'
        parentExecutionId:
          description: The run that started this one as a sub-workflow, if any
          type:
            - string
            - 'null'
        restartOf:
          description: The run this one restarts, if any
          type:
            - string
            - 'null'
        rootExecutionId:
          description: The top of this run's tree of runs (itself when it has no parent)
          type:
            - string
            - 'null'
        startTime:
          description: The start time of the execution, with the server's UTC offset
          format: date-time
          type: string
        status:
          description: The execution status
          type: string
        workflowId:
          description: The workflow identifier
          type: string
      type: object
    FieldError:
      description: Field-specific validation error detail
      properties:
        field:
          description: The name of the field that failed validation
          example: sessionId
          type: string
        message:
          description: The validation error message explaining the failure
          example: 'Session not found: ''unknown-session'''
          type: string
      type: object
    Nodes:
      description: How far a run got through its nodes
      properties:
        done:
          description: Nodes in a final state
          format: int32
          type: integer
        failed:
          description: The first node that failed, if any
          type:
            - string
            - 'null'
        total:
          description: Nodes in the run
          format: int32
          type: integer
      type: object
  securitySchemes:
    bearerAuth:
      scheme: bearer
      type: http
    apiKeyAuth:
      in: header
      name: X-API-Key
      type: apiKey

````

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