Google Cloud Dataflow · Arazzo Workflow

Google Cloud Dataflow Diagnose Job

Version 1.0.0

Read a job's state, pull its error-level messages, then inspect stage execution details.

1 workflow 2 source APIs 1 provider
View Spec View on GitHub Apache BeamBatch ProcessingBig DataData ProcessingETLStream ProcessingArazzoWorkflows

Provider

google-cloud-dataflow

Workflows

diagnose-job
Read job state, pull error messages, and inspect execution details.
Reads a job's current state, retrieves its error-level status messages, then pulls execution details to surface failing stages.
3 steps inputs: accessToken, jobId, location, projectId outputs: currentState, jobMessages, stages
1
readJob
Read the job to capture its current state as the starting point for diagnosis.
2
pullErrorMessages
Retrieve the job status messages filtered to error importance to surface failures reported during execution.
3
inspectExecutionDetails
Pull the stage-level execution details for the job so failing stages and their progress can be identified.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Google Cloud Dataflow Diagnose Job
  summary: Read a job's state, pull its error-level messages, then inspect stage execution details.
  description: >-
    Gathers the signals needed to diagnose a problematic Dataflow job. The
    workflow reads the job to capture its current state, retrieves the job status
    messages filtered to error importance, then pulls the stage-level execution
    details so failing stages can be identified. Every step spells out its
    request inline, including the inline Bearer authorization Google Cloud
    requires, so the flow can be read and executed without opening the underlying
    OpenAPI description.
  version: 1.0.0
sourceDescriptions:
- name: jobsApi
  url: ../openapi/google-cloud-dataflow-jobs-api-openapi.yml
  type: openapi
- name: messagesApi
  url: ../openapi/google-cloud-dataflow-messages-api-openapi.yml
  type: openapi
workflows:
- workflowId: diagnose-job
  summary: Read job state, pull error messages, and inspect execution details.
  description: >-
    Reads a job's current state, retrieves its error-level status messages, then
    pulls execution details to surface failing stages.
  inputs:
    type: object
    required:
    - accessToken
    - projectId
    - location
    - jobId
    properties:
      accessToken:
        type: string
        description: Google Cloud OAuth 2.0 access token used as a Bearer credential.
      projectId:
        type: string
        description: The Google Cloud project id that owns the job.
      location:
        type: string
        description: The regional endpoint that contains the job (e.g. us-central1).
      jobId:
        type: string
        description: The id of the job to diagnose.
  steps:
  - stepId: readJob
    description: >-
      Read the job to capture its current state as the starting point for
      diagnosis.
    operationId: getLocationJob
    parameters:
    - name: Authorization
      in: header
      value: Bearer $inputs.accessToken
    - name: projectId
      in: path
      value: $inputs.projectId
    - name: location
      in: path
      value: $inputs.location
    - name: jobId
      in: path
      value: $inputs.jobId
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      currentState: $response.body#/currentState
  - stepId: pullErrorMessages
    description: >-
      Retrieve the job status messages filtered to error importance to surface
      failures reported during execution.
    operationId: listLocationJobMessages
    parameters:
    - name: Authorization
      in: header
      value: Bearer $inputs.accessToken
    - name: projectId
      in: path
      value: $inputs.projectId
    - name: location
      in: path
      value: $inputs.location
    - name: jobId
      in: path
      value: $inputs.jobId
    - name: minimumImportance
      in: query
      value: JOB_MESSAGE_ERROR
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      jobMessages: $response.body#/jobMessages
      nextPageToken: $response.body#/nextPageToken
  - stepId: inspectExecutionDetails
    description: >-
      Pull the stage-level execution details for the job so failing stages and
      their progress can be identified.
    operationId: getLocationJobExecutionDetails
    parameters:
    - name: Authorization
      in: header
      value: Bearer $inputs.accessToken
    - name: projectId
      in: path
      value: $inputs.projectId
    - name: location
      in: path
      value: $inputs.location
    - name: jobId
      in: path
      value: $inputs.jobId
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      stages: $response.body#/stages
  outputs:
    currentState: $steps.readJob.outputs.currentState
    jobMessages: $steps.pullErrorMessages.outputs.jobMessages
    stages: $steps.inspectExecutionDetails.outputs.stages

Work with this as data

Every workflow here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for arazzo workflows

4 MCP tools reach this
  • find_arazzoBrowse and filter every workflow in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This workflow
curl "https://apis.io/api/v1/arazzo/google-cloud-dataflow-diagnose-job-workflow"
All arazzo workflows
curl "https://apis.io/api/v1/arazzo?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.