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

# Get pipeline execution details

> Retrieve detailed information about a pipeline execution including:
- Overall pipeline status
- Individual job statuses for each node
- Node execution information (execution count, duration, errors)
- Job status summary




## OpenAPI

````yaml /api-reference/openapi.yaml get /pipeline/{id}
openapi: 3.0.3
info:
  title: FlowDrop™ API
  description: >
    FlowDrop is a visual workflow editor for AI applications and data processing
    pipelines.

    This API provides comprehensive endpoints for managing workflows, node
    types, pipeline execution, and port configuration.


    ## Features

    - **Workflow Management**: Complete CRUD operations for workflows with nodes
    and edges

    - **Node Type Discovery**: Browse and search available node processors with
    metadata

    - **Pipeline Execution**: Execute workflows with real-time status tracking
    and job management

    - **Port Configuration**: Dynamic port compatibility system with data type
    management

    - **Real-time Updates**: Track node execution status and pipeline progress

    - **Import/Export**: Import and export workflows in JSON format

    - **Validation**: Workflow validation before execution

    - **Agent Spec Integration**: Import/export Oracle Open Agent Spec flows and
    execute on compatible runtimes (WayFlow/PyAgentSpec)


    ## Architecture

    - **Frontend**: Svelte 5 + XYFlow for visual workflow editing

    - **Backend**: Drupal 10/11 with custom node processor plugins

    - **API**: RESTful JSON API with consistent response format

    - **Storage**: Drupal entity system with workflow versioning


    ## Authentication

    API endpoints require Drupal authentication. Use Bearer token or
    session-based authentication.


    ## Rate Limiting

    - Node Discovery: 100 requests/minute

    - Workflow Operations: 50 requests/minute

    - Pipeline Execution: 20 requests/minute


    ## Error Handling

    All errors return a consistent format with success flag, error message, and
    optional details.
  version: 1.0.0
  contact:
    name: FlowDrop Support
    email: shibinkidd@gmail.com
    url: https://www.drupal.org/project/issues/flowdrop?categories=All
servers:
  - url: http://localhost:5173/api/flowdrop
    description: Local development server (Svelte)
  - url: https://flowdrop.ddev.site/api/flowdrop
    description: Local Drupal server
security:
  - BearerAuth: []
  - SessionAuth: []
tags:
  - name: System
    description: System health and status endpoints
  - name: Node Types
    description: Node type discovery and metadata endpoints
  - name: Configuration
    description: System configuration endpoints including port configuration
  - name: Workflows
    description: Workflow CRUD operations
  - name: Pipeline
    description: Pipeline execution and monitoring
  - name: Playground
    description: Interactive workflow testing and chat interface
  - name: Interrupts
    description: |
      Human-in-the-Loop (HITL) interrupt endpoints for workflow interactions.
      Interrupts allow workflows to pause execution and request user input.
  - name: Validation
    description: Workflow validation
  - name: Import/Export
    description: Workflow import and export operations
  - name: Chat
    description: |
      LLM Chat Interface for natural language workflow building.
      Translates user intent into DSL commands via a backend LLM integration.
  - name: Agent Spec
    description: >
      Oracle Open Agent Spec integration endpoints.

      Provides bidirectional conversion between FlowDrop workflows and Agent
      Spec format,

      plus runtime execution on compatible runtimes (WayFlow, PyAgentSpec).

      @see https://github.com/oracle/agent-spec
paths:
  /pipeline/{id}:
    get:
      tags:
        - Pipeline
      summary: Get pipeline execution details
      description: |
        Retrieve detailed information about a pipeline execution including:
        - Overall pipeline status
        - Individual job statuses for each node
        - Node execution information (execution count, duration, errors)
        - Job status summary
      operationId: getPipeline
      parameters:
        - name: id
          in: path
          description: Pipeline UUID
          required: true
          schema:
            type: string
            format: uuid
      responses:
        '200':
          description: Pipeline details retrieved successfully
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/PipelineDetailResponse'
              example:
                status: running
                jobs:
                  - id: job-1
                    node_id: node-1
                    status: completed
                    execution_count: 5
                    started: '2024-01-20T10:00:00Z'
                    completed: '2024-01-20T10:00:05Z'
                    execution_time: 5000
                  - id: job-2
                    node_id: node-2
                    status: running
                    execution_count: 3
                    started: '2024-01-20T10:00:05Z'
                node_statuses:
                  node-1:
                    status: completed
                    last_executed: '2024-01-20T10:00:05Z'
                    execution_time: 5000
                  node-2:
                    status: running
                    last_executed: '2024-01-20T10:00:05Z'
                job_status_summary:
                  total: 5
                  pending: 0
                  running: 1
                  completed: 3
                  failed: 1
                  cancelled: 0
        '404':
          $ref: '#/components/responses/NotFound'
        '500':
          $ref: '#/components/responses/InternalServerError'
components:
  schemas:
    PipelineDetailResponse:
      type: object
      properties:
        status:
          type: string
          enum:
            - pending
            - running
            - completed
            - failed
            - cancelled
            - paused
            - interrupted
          description: Overall pipeline status
        jobs:
          type: array
          items:
            $ref: '#/components/schemas/JobStatus'
          description: Individual job statuses
        node_statuses:
          type: object
          additionalProperties:
            $ref: '#/components/schemas/NodeStatus'
          description: Node execution statuses keyed by node ID
        job_status_summary:
          $ref: '#/components/schemas/JobStatusSummary'
        kanban_config:
          $ref: '#/components/schemas/KanbanConfig'
          description: >-
            Optional server-defined kanban board layout; frontend falls back to
            defaults if absent
      required:
        - status
        - jobs
        - node_statuses
        - job_status_summary
    JobStatus:
      type: object
      properties:
        id:
          type: string
          description: Job UUID
        node_id:
          type: string
          description: Node instance UUID
        status:
          $ref: '#/components/schemas/NodeExecutionStatus'
        execution_count:
          type: integer
          description: Number of times executed
        started:
          type: string
          format: date-time
          description: Job start time
        completed:
          type: string
          format: date-time
          description: Job completion time
        execution_time:
          type: integer
          description: Execution time in milliseconds
        error_message:
          type: string
          description: Error message if failed
    NodeStatus:
      type: object
      properties:
        status:
          $ref: '#/components/schemas/NodeExecutionStatus'
        last_executed:
          type: string
          format: date-time
        execution_time:
          type: integer
          description: Last execution time in milliseconds
        error:
          type: string
          description: Last error message
    JobStatusSummary:
      type: object
      properties:
        total:
          type: integer
          description: Total number of jobs
        pending:
          type: integer
          description: Number of pending jobs
        running:
          type: integer
          description: Number of running jobs
        completed:
          type: integer
          description: Number of completed jobs
        failed:
          type: integer
          description: Number of failed jobs
        cancelled:
          type: integer
          description: Number of cancelled jobs
        skipped:
          type: integer
          description: Number of skipped jobs
        paused:
          type: integer
          description: Number of paused jobs
        interrupted:
          type: integer
          description: Number of interrupted jobs
      required:
        - total
        - pending
        - running
        - completed
        - failed
        - cancelled
    KanbanConfig:
      type: object
      properties:
        columns:
          type: array
          items:
            $ref: '#/components/schemas/KanbanColumnDef'
          description: Ordered list of kanban columns to display
      required:
        - columns
    ErrorResponse:
      allOf:
        - $ref: '#/components/schemas/ApiResponse'
        - type: object
          properties:
            success:
              type: boolean
              example: false
            error:
              type: string
              description: Error message
            code:
              type: string
              description: Error code
            details:
              type: object
              description: Additional error details
    NodeExecutionStatus:
      type: string
      enum:
        - idle
        - pending
        - running
        - completed
        - failed
        - cancelled
        - skipped
        - paused
        - interrupted
      description: Current execution status of a node
    KanbanColumnDef:
      type: object
      properties:
        key:
          type: string
          description: Unique column identifier
        label:
          type: string
          description: Display label for the column
        statuses:
          type: array
          items:
            $ref: '#/components/schemas/NodeExecutionStatus'
          description: Node statuses that belong to this column
        icon:
          type: string
          description: Iconify icon name (e.g. mdi:clock-outline)
        color:
          type: string
          description: CSS color value for the column accent (e.g. var(--fd-warning) or
      required:
        - key
        - label
        - statuses
    ApiResponse:
      type: object
      properties:
        success:
          type: boolean
          description: Whether the request was successful
        data:
          description: Response data (type varies by endpoint)
        message:
          type: string
          description: Response message
        error:
          type: string
          description: Error message (if any)
  responses:
    NotFound:
      description: Resource not found
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
          example:
            success: false
            error: Resource not found
            code: NOT_FOUND
    InternalServerError:
      description: Internal server error
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
          example:
            success: false
            error: Internal server error
            code: INTERNAL_ERROR
  securitySchemes:
    BearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: JWT token for authentication
    SessionAuth:
      type: apiKey
      in: cookie
      name: SESS
      description: Drupal session cookie

````