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

# Get Workflow Run Detail

> Retrieve the current execution results of a workflow task based on the workflow execution ID.



## OpenAPI

````yaml /en/api-reference/openapi_chatflow.json get /workflows/run/{workflow_run_id}
openapi: 3.0.1
info:
  title: Chatflow App API
  description: >-
    Chatflow applications support session persistence, allowing previous chat
    history to be used as context for responses. Chatflow apps use the
    `advanced-chat` mode, providing workflow-level streaming events for detailed
    execution tracking including node starts, finishes, iterations, and workflow
    lifecycle.
  version: 1.0.0
servers:
  - url: '{api_base_url}'
    description: >-
      The base URL for the Chatflow App API. Replace {api_base_url} with the
      actual API base URL provided for your application.
    variables:
      api_base_url:
        default: https://api.dify.ai/v1
        description: Actual base URL of the API
security:
  - ApiKeyAuth: []
tags:
  - name: Chatflows
    description: >-
      Operations for Chatflow apps, including chat messaging, workflow run
      details, and event streaming.
  - name: Files
    description: File upload and preview operations.
  - name: End Users
    description: Operations related to end user information.
  - name: Feedback
    description: User feedback operations.
  - name: Conversations
    description: Operations related to managing conversations.
  - name: TTS
    description: Text-to-Speech and Speech-to-Text operations.
  - name: Applications
    description: Operations to retrieve application settings and information.
  - name: Annotations
    description: Operations related to managing annotations for direct replies.
  - name: Human Input
    description: Endpoints for resuming paused workflows that require human input.
paths:
  /workflows/run/{workflow_run_id}:
    get:
      tags:
        - Chatflows
      summary: Get Workflow Run Detail
      description: >-
        Retrieve the current execution results of a workflow task based on the
        workflow execution ID.
      operationId: getChatflowWorkflowRunDetail
      parameters:
        - name: workflow_run_id
          in: path
          required: true
          description: >-
            Workflow run ID, can be obtained from the streaming events or
            message metadata.
          schema:
            type: string
      responses:
        '200':
          description: Successfully retrieved workflow run details.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/WorkflowRunDetailResponse'
              examples:
                workflowRunDetail:
                  summary: Response Example
                  value:
                    id: fb47b2e6-5e43-4f90-be01-d5c5a088d156
                    workflow_id: 7c3e33d4-2a8b-4e5f-9b1a-d3c6e8f12345
                    status: succeeded
                    inputs:
                      query: Translate this to French
                    outputs:
                      result: Traduisez ceci en francais
                    error: null
                    total_steps: 3
                    total_tokens: 150
                    created_at: 1705407629
                    finished_at: 1705407630
                    elapsed_time: 1.23
        '400':
          description: '`not_workflow_app` : App mode does not match the API route.'
          content:
            application/json:
              examples:
                not_workflow_app:
                  summary: not_workflow_app
                  value:
                    status: 400
                    code: not_workflow_app
                    message: Please check if your app mode matches the right API route.
        '404':
          description: '`not_found` : Workflow run not found.'
          content:
            application/json:
              examples:
                workflow_run_not_found:
                  summary: not_found
                  value:
                    status: 404
                    code: not_found
                    message: Workflow run not found.
components:
  schemas:
    WorkflowRunDetailResponse:
      type: object
      properties:
        id:
          type: string
          format: uuid
          description: Workflow run ID.
        workflow_id:
          type: string
          format: uuid
          description: Workflow ID.
        status:
          type: string
          description: >-
            Workflow execution status. `running` for in-progress executions,
            `succeeded` when completed successfully, `failed` when execution
            encountered an error, `stopped` when manually halted,
            `partial-succeeded` when some nodes succeeded but others failed,
            `paused` when awaiting human input.
        inputs:
          type: object
          additionalProperties: true
          description: Input variables for the workflow run.
        outputs:
          type: object
          additionalProperties: true
          nullable: true
          description: Output data from the workflow.
        error:
          type: string
          nullable: true
          description: Error message if the workflow failed.
        total_steps:
          type: integer
          description: Total number of workflow steps executed.
        total_tokens:
          type: integer
          description: Total tokens consumed.
        created_at:
          type: integer
          format: int64
          description: Unix timestamp of when the workflow run was created.
        finished_at:
          type: integer
          format: int64
          nullable: true
          description: Unix timestamp of when the workflow run finished.
        elapsed_time:
          type: number
          format: float
          nullable: true
          description: Total time elapsed in seconds.
  securitySchemes:
    ApiKeyAuth:
      type: http
      scheme: bearer
      bearerFormat: API_KEY
      description: >-
        API Key authentication. For all API requests, include your API Key in
        the `Authorization` HTTP Header, prefixed with `Bearer `. Example:
        `Authorization: Bearer {API_KEY}`. **Strongly recommend storing your API
        Key on the server-side, not shared or stored on the client-side, to
        avoid possible API-Key leakage that can lead to serious consequences.**

````