Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML & AI
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
    • Yandex Cloud Partner program
  • Blog
  • Pricing
  • Documentation
© 2025 Direct Cursus Technology L.L.C.
Yandex Serverless Integrations
    • All guides
        • Getting a list of workflow executions
        • Getting the workflow execution information
        • Getting information on the progress of each step
    • Viewing operations with service resources
  • Pricing policy
  • Terraform reference
  • Release notes
  1. Step-by-step guides
  2. Workflows
  3. Getting the workflow execution information
  4. Getting information on the progress of each step

Getting detailed information on the progress of each workflow step

Written by
Yandex Cloud
Updated at May 5, 2025
Management console
CLI
API
  1. In the management console, navigate to the folder containing the workflow execution.
  2. Select Serverless Integrations.
  3. In the left-hand panel, click Workflows and select a workflow.
  4. In the left-hand panel, click Executions and select an execution.
  5. In the left-hand panel, click Timeline. The Timeline page will display the chart of the workflow execution steps.
  6. 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.

If you do not have the Yandex Cloud CLI yet, install and initialize it.

The folder specified when creating the CLI profile is used by default. To change the default folder, use the yc config set folder-id <folder_ID> command. You can specify a different folder using the --folder-name or --folder-id parameter.

  1. See the description of the CLI command to view the workflow execution information:

    yc serverless workflow execution get-history --help
    
  2. Get a list of workflows:

    yc serverless workflow list
    

    Result:

    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********
    
  3. Specify a workflow ID to get a list of workflow executions:

    yc serverless workflow execution list --workflow-id <workflow_ID>
    

    Result:

    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
    
  4. To get detailed information on the progress of each workflow execution step, specify the execution ID:

    yc serverless workflow execution get-history <execution_ID>
    

    Result:

    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"
    

To get detailed information on the progress of each workflow execution step, use the getHistory REST API method for the Execution resource or the WorkflowsService/GetHistory gRPC API call.

Was the article helpful?

Previous
Getting the workflow execution information
Next
Starting a workflow
© 2025 Direct Cursus Technology L.L.C.