[Yandex Cloud documentation](../../../../index.md) > [Yandex Serverless Integrations](../../../index.md) > [Step-by-step guides](../../index.md) > Workflows > Getting workflow execution info > Getting information on the progress of each step

# Getting detailed information on the progress of each workflow step

{% list tabs group=instructions %}

- Management console {#console}

  1. In the [management console](https://console.yandex.cloud), navigate to the folder containing the [workflow execution](../../../concepts/workflows/execution.md).
  1. Navigate to **Serverless Integrations**.
  1. In the left-hand panel, click ![image](../../../../_assets/console-icons/graph-node.svg) **Workflows** and select a workflow.
  1. In the left-hand panel, click ![image](../../../../_assets/console-icons/bars-play.svg) **Executions** and select an execution.
  1. In the left-hand panel, click ![image](../../../../_assets/console-icons/timeline.svg) **Timeline**. The **Timeline** page will display the chart of the workflow execution steps.
  1. Click the bar of the step of your choice. The **Overview**, **Input data**, and **Output data** tabs at the bottom of the screen will display detailed information about the step progress.

- CLI {#cli}

  If you do not have the Yandex Cloud CLI yet, [install and initialize it](../../../../cli/quickstart.md#install).

  The folder used by default is the one specified when [creating](../../../../cli/operations/profile/profile-create.md) the CLI profile. To change the default folder, use the `yc config set folder-id <folder_ID>` command. You can also specify a different folder for any command using `--folder-name` or `--folder-id`. If you access a resource by its name, the search will be limited to the default folder. If you access a resource by its ID, the search will be global, i.e., through all folders based on access permissions.

  1. See the description of the CLI command to view the [workflow execution](../../../concepts/workflows/execution.md) information:

      ```bash
      yc serverless workflow execution get-history --help
      ```

  1. Get a list of workflows:
     
     ```bash
     yc serverless workflow list
     ```
     
     Result:
     
     ```text
     workflows:
       - id: dfqdi6ic7c5j********
         folder_id: b1g681qpemb4********
         created_at: "2025-03-10T13:31:55.387059Z"
         name: workflow895
         status: ACTIVE
         log_options:
           folder_id: b1g681qpemb4********
       ...
       - id: dfqud9cbc4k5********
         folder_id: b1g681qpemb4********
         created_at: "2025-03-10T12:57:48.679682Z"
         name: workflow203
         status: ACTIVE
         log_options:
           folder_id: b1g681qpemb4********
     ```
  1. Specify a workflow ID to get a list of workflow executions:
     
     ```bash
     yc serverless workflow execution list --workflow-id <workflow_ID>
     ```
     
     Result:
     
     ```text
     executions:
       - id: dfq...e78
         workflow_id: dfqud9cbc4k5********
         status: FINISHED
         started_at: "2025-03-10T15:54:44.304781814Z"
         duration: 1.070697344s
       ...
       - id: dfq...4d5
         workflow_id: dfqud9cbc4k5********
         status: FINISHED
         started_at: "2025-03-10T15:05:19.982768956Z"
         duration: 0.971907165s
     ```
  1. To get detailed information on the progress of each workflow execution step, specify the execution ID:

      ```bash
      yc serverless workflow execution get-history <execution_ID>
      ```

      Result:

      ```text
      id: dfq...e78
      workflow_id: dfqud9cbc4k5********
      status: FINISHED
      started_at: "2025-03-10T15:54:44.304781814Z"
      duration: 1.070697344s
      entries:
        - id: fetch_posts
          started_at: "2025-03-10T15:54:44.452347159Z"
          duration: 0.795435385s
          input:
            input_json: '{"input":{}}'
          output:
            output_json:
            ...
          status: COMPLETED
          type: HttpCall
          attempts: "1"
        ...
        - id: fetch_users
          started_at: "2025-03-10T15:54:44.452394388Z"
          duration: 0.751175310s
          input:
            input_json: '{"input":{}}'
          output:
            output_json:
            ...
          status: COMPLETED
          type: HttpCall
          attempts: "1"
      ```

- API {#api}

  To get detailed information on the progress of each [workflow execution](../../../concepts/workflows/execution.md) step, use the [getHistory](../../../workflows/api-ref/Execution/getHistory.md) REST API method for the [Execution](../../../workflows/api-ref/Execution/index.md) resource or the [WorkflowsService/GetHistory](../../../workflows/api-ref/grpc/Execution/getHistory.md) gRPC API call.

{% endlist %}