> ## 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 Annotation Reply Job Status

> Retrieves the status of an asynchronous annotation reply configuration job started by [Configure Annotation Reply](/api-reference/annotations/configure-annotation-reply).



## OpenAPI

````yaml /en/api-reference/openapi_chatflow.json get /apps/annotation-reply/{action}/status/{job_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:
  /apps/annotation-reply/{action}/status/{job_id}:
    get:
      tags:
        - Annotations
      summary: Get Annotation Reply Job Status
      description: >-
        Retrieves the status of an asynchronous annotation reply configuration
        job started by [Configure Annotation
        Reply](/api-reference/annotations/configure-annotation-reply).
      operationId: getAdvancedInitialAnnotationReplySettingsStatus
      parameters:
        - name: action
          in: path
          required: true
          description: >-
            Action type, must match the [Configure Annotation
            Reply](/api-reference/annotations/configure-annotation-reply) call.
          schema:
            type: string
            enum:
              - enable
              - disable
        - name: job_id
          in: path
          required: true
          description: >-
            Job ID returned by [Configure Annotation
            Reply](/api-reference/annotations/configure-annotation-reply).
          schema:
            type: string
            format: uuid
      responses:
        '200':
          description: Successfully retrieved task status.
          content:
            application/json:
              schema:
                $ref: >-
                  #/components/schemas/InitialAnnotationReplySettingsStatusResponse
              examples:
                jobStatus:
                  summary: Response Example
                  value:
                    job_id: a1b2c3d4-5678-90ab-cdef-1234567890ab
                    job_status: completed
                    error_msg: ''
        '400':
          description: '`invalid_param` : The specified job does not exist.'
          content:
            application/json:
              examples:
                invalid_param:
                  summary: invalid_param
                  value:
                    status: 400
                    code: invalid_param
                    message: The job does not exist.
components:
  schemas:
    InitialAnnotationReplySettingsStatusResponse:
      type: object
      properties:
        job_id:
          type: string
          format: uuid
          description: >-
            Job ID from the [Configure Annotation
            Reply](/api-reference/annotations/configure-annotation-reply) call.
        job_status:
          type: string
          description: >-
            Current job status. `waiting` for queued, `processing` for in
            progress, `completed` when finished, `error` if failed.
        error_msg:
          type: string
          description: >-
            Error message describing why the job failed. Empty string when
            `job_status` is not `error`.
  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.**

````