> ## Documentation Index > Fetch the complete documentation index at: https://astronomer.io/docs/llms.txt > Use this file to discover all available pages before exploring further. # Get the diagnosis of a Dag-failure diagnosis run > Returns the diagnosis of a completed Dag-failure diagnosis run: title, summary, root cause, suggested fix and evidence. While the run is pending or running, this returns 409; poll the run's status until it is completed, then call this again. A run that failed or timed out, or whose diagnosis is no longer available, also returns 409. ## OpenAPI ````yaml /astro/api/v-1-labs/openapi.yaml get /organizations/{organizationId}/observability/deployments/{deploymentId}/dag-failure-diagnosis/runs/{diagnosisRunId}/result openapi: 3.0.3 info: contact: {} description: >- Astro Labs API - Experimental endpoints for preview features, plus everything served under /v1. title: Astro Labs API version: v1.1 servers: - url: /labs/v1.1 security: - JWT: [] tags: - description: >- Canned-data placeholder used to exercise the labs epoch versioning surface. Real labs endpoints register their own tags. name: Example - description: >- The `organization` object contains the metadata and configurations of an Astro Organization. It does not include objects within the Organization, such as users and clusters. Make requests to `organization` endpoints to view and update high level settings for your Organization, including settings related to authentication and billing. To manage resources within an Organization, make requests to the endpoints related to those resources, such as `users`. See [Billing](https://astronomer.io/docs/astro/manage-billing), [Set up single sign-on](https://astronomer.io/docs/astro/configure-idp), and [Manage domains](https://astronomer.io/docs/astro/manage-domains). name: Organization - description: >- The `deployment` object represents an Astro Deployment, which is a hosted Airflow environment that is powered by all core Airflow components, including schedulers and workers. Make requests to the `deployment` object to create, update, or delete a Deployment or its computational resources. See [Deployment settings](https://astronomer.io/docs/astro/deployment-settings). name: Deployment - description: >- A `cluster` object represents an Astro cluster, which is a Kubernetes cluster that hosts the infrastructure required to run Deployments. Make requests to `cluster` endpoints to manage your standard and dedicated clusters. See [Create a dedicated cluster](https://astronomer.io/docs/astro/create-dedicated-cluster). name: Cluster - description: >- The `workspace` object represents an Astro Workspace, which is a collection of Deployments that can be accessed by a specific group of users. It contains metadata about a Workspace, but does not contain objects within the Workspace such as users and Deployments. Make requests to `workspace` endpoints to manage high level details about your Workspace. To manage resources within a Workspace, make requests to the endpoints related to those resources, such as `users`, and use the `workspaceIds` parameter to filter results by Workspace. See [Configure Workspaces](https://astronomer.io/docs/astro/manage-workspaces). name: Workspace - description: >- The `user` object represents a user account in your Astro Organization. Astro creates a new `user` object whenever you invite a user by email or add a user to Astro through an identity provider. The object contains all information about a user, including their personal information, roles, and login attempts. It doesn't include attributes for actions that the user completes after they log in, such as updating a Deployment. Make requests to `user` endpoints to manage permissions for existing users both at the Organization and Workspace level. To create new users, make requests to `invite` endpoints instead. name: User - description: >- The `team` object represents an Astro Team, which is a group of users that share the same permissions across your Organization and Workspaces. Make requests to `team` endpoints to create, update, and delete Teams across an Organization. See [Configure Teams on Astro](https://astronomer.io/docs/astro/manage-teams). name: Team - description: >- The `apitoken` object represents a single API token within your Organization. API tokens are used to authenticate automated tools and processes to your Organization. They have varying levels of access to your resources based on their Organization, Workspace, and Deployment roles. See [Workspace API tokens](workspace-api-tokens.md) and [Organization API tokens](organization-api-tokens.md). name: api-token x-group: API Token - name: allowed-ip-address-range x-group: Allowed IP Address Range - name: agent-token x-group: Agent Token - name: notification-channels x-group: Notification Channels paths: /organizations/{organizationId}/observability/deployments/{deploymentId}/dag-failure-diagnosis/runs/{diagnosisRunId}/result: get: tags: - Observability summary: Get the diagnosis of a Dag-failure diagnosis run description: >- Returns the diagnosis of a completed Dag-failure diagnosis run: title, summary, root cause, suggested fix and evidence. While the run is pending or running, this returns 409; poll the run's status until it is completed, then call this again. A run that failed or timed out, or whose diagnosis is no longer available, also returns 409. operationId: LabsGetDagFailureDiagnosisResult parameters: - description: The ID of the Organization to which the Deployment belongs. in: path name: organizationId required: true schema: type: string - description: The Deployment's ID. in: path name: deploymentId required: true schema: type: string - description: The diagnosis run ID. in: path name: diagnosisRunId required: true schema: format: uuid type: string responses: '200': content: application/json: schema: $ref: '#/components/schemas/RcaSessionDiagnosis' description: OK '400': content: application/json: schema: $ref: '#/components/schemas/Error' description: Bad Request '401': content: application/json: schema: $ref: '#/components/schemas/Error' description: Unauthorized '403': content: application/json: schema: $ref: '#/components/schemas/Error' description: Forbidden '404': content: application/json: schema: $ref: '#/components/schemas/Error' description: Not Found '409': content: application/json: schema: $ref: '#/components/schemas/Error' description: Conflict '500': content: application/json: schema: $ref: '#/components/schemas/Error' description: Internal Server Error '503': content: application/json: schema: $ref: '#/components/schemas/Error' description: Service Unavailable security: - JWT: [] components: schemas: RcaSessionDiagnosis: properties: confidence: type: number confidence_justification: type: string contributing_factors: items: type: string type: array coverage_quality: description: Coverage quality type: string dag_level_checks: description: Diagnostic checks items: $ref: '#/components/schemas/RcaCheck' type: array evidence: description: Evidence items: $ref: '#/components/schemas/RcaEvidenceItem' type: array evidence_gaps: items: $ref: '#/components/schemas/RcaEvidenceGap' type: array evidence_status: enum: - confirmed - hypothesis - insufficient_evidence type: string exception_class: type: string exception_message: type: string failure_onset_date: description: Temporal context type: string from_dag_run_id: description: >- Provenance fields layered on by core / polaris-agent after the LLM emits: - FromDagRunId: original dag_run_id when this diagnosis was replayed from the polaris-agent dedup cache (absent on fresh diagnoses). - SessionId: durable id of the RCA session row this diagnosis was emitted from. type: string last_success_date: type: string log_classification: type: string log_snippet: description: Log analysis type: string priority: type: string root_cause: description: Root cause type: string root_cause_task: type: string root_cause_type: type: string session_id: type: string severity: description: Severity & confidence type: string suggested_fix: description: Remediation type: string summary: type: string tasks: items: $ref: '#/components/schemas/RcaTaskDiagnosis' type: array title: description: Core identification type: string transience: type: string required: - summary - title type: object Error: properties: fieldErrors: description: >- FieldErrors carries one entry per failed request-validation constraint. Only present on 400 responses caused by request binding/validation. items: $ref: '#/components/schemas/FieldValidationError' type: array message: type: string requestId: type: string statusCode: maximum: 600 minimum: 400 type: integer required: - message - requestId - statusCode type: object RcaCheck: properties: check: type: string detail: type: string passed: type: boolean required: - check type: object RcaEvidenceItem: properties: dag_id: type: string dag_run_id: type: string kind: enum: - note - log - code - other type: string text: type: string required: - kind - text type: object RcaEvidenceGap: properties: detail: type: string field_name: type: string why_missing: enum: - attempted_no_data - not_attempted - not_applicable type: string required: - field_name type: object RcaTaskDiagnosis: properties: checks: items: $ref: '#/components/schemas/RcaCheck' type: array first_attempt_error: type: string task_id: type: string task_ran: type: boolean required: - task_id type: object FieldValidationError: properties: code: type: string field: type: string message: type: string required: - code - field - message type: object securitySchemes: JWT: scheme: bearer type: http ````