---
title: "Get a task from the registry"
method: GET
path: "/sources/{sourceKey}/v1/tasks/{taskId}"
tags: ["Task"]
---

# Get a task from the registry

`GET /sources/{sourceKey}/v1/tasks/{taskId}`

Get the operation receipts related to a task id.

## Path parameters

- `sourceKey` string, required
- `taskId` string, required — The task identifier. Used to track an async task in the system. Use the task ID to poll for completion status. The taskId holds different prefix to represent different tasks. - oneOf task: `s_<id>`. - bulk task: `bk_<id>` (deprecated: `<id>` only). - bundle task: `bd_<id>` (deprecated: `<id>` only). - purge task: `pg_<id>` (deprecated: `purge:<id>`).

## Query parameters

- `withReceipts` boolean

## Response `200`

The task with the given id.

- V1Task
  - `status` 'SUCCESS' | 'PENDING' | 'CANCELLED' | 'FAILURE', required — Status of the task. * `SUCCESS`: All the operations of the task completed successfully. * `PENDING`: At least one operation in the task is still pending. * `CANCELLED`: All the operations in the task were cancelled. * `FAILURE`: At least one operations failed or was cancelled.
  - `taskId` string, required — The task identifier. Used to track an async task in the system. Use the task ID to poll for completion status. The taskId holds different prefix to represent different tasks. - oneOf task: `s_<id>`. - bulk task: `bk_<id>` (deprecated: `<id>` only). - bundle task: `bd_<id>` (deprecated: `<id>` only). - purge task: `pg_<id>` (deprecated: `purge:<id>`).
  - `receipts` V1OperationReceipt[]
    - union
      - object
        - `receivedAt` string, date-time, required — The time the operation was received.
        - `completedAt` string, date-time — The time the operation was completed (whether successfully or not).
        - `taskId` string, required — The task identifier. Used to track an async task in the system. Use the task ID to poll for completion status. The taskId holds different prefix to represent different tasks. - oneOf task: `s_<id>`. - bulk task: `bk_<id>` (deprecated: `<id>` only). - bundle task: `bd_<id>` (deprecated: `<id>` only). - purge task: `pg_<id>` (deprecated: `purge:<id>`).
        - `action` 'CREATE' | 'UPSERT' | 'DELETE' | 'UPDATE', required — The action to perform.
        - `status` 'SUCCESS' | 'PENDING' | 'CANCELLED' | 'FAILURE', required — Status of the operation. * `SUCCESS`: The operation was persisted in the source, or was dropped by a reject action of the user. * `PENDING`: The operation is being processed asyncronously by the system or is in a pipeline IN_REVIEW status. * `CANCELLED`: The operation was cancelled by the system due to a concurrent operation. * `FAILURE`: The operation failed due to validation or processing error.
        - `error` V1Error
          - `code` 400 | 401 | 403 | 404 | 408 | 409 | 413 | 500 | 501, required
          - `message` string, required
          - `type` 'ALREADY_EXISTS' | 'FAILED_PRECONDITION' | 'INTERNAL' | 'INVALID_ARGUMENT' | 'NOT_FOUND' | 'OUT_OF_RANGE' | 'UNIMPLEMENTED' | 'PERMISSION_DENIED' | 'UNAUTHENTICATED' | 'CONTENT_TOO_LARGE' | 'REQUEST_TIMEOUT', required
          - `details` V1Error[] — list of errors that occurred if applicable.
        - `pipelineExecution` V1PipelineExecutionInfo
          - `id` string, required — The id of the pipeline execution.
          - `pipelineDefinitionId` string, required — The id with version in the format `<id>.<version>`.
          - `status` 'SUCCESSFUL' | 'ERROR' | 'IN_PROGRESS' | 'IN_REVIEW' | 'CANCELLED' | 'DROPPED', required — Status of the pipeline execution. * `SUCCESSFUL`: The pipeline execution completed successfully. Every step of the pipeline was executed successfully and the change has been accepted in the system. * `ERROR`: The pipeline execution failed at a step due to a system error. * `IN_PROGRESS`: The pipeline execution is being processed by the system. * `IN_REVIEW`: The pipeline execution is waiting for a manual action. Refer to the ActOnPipelineExecution endpoint. * `CANCELLED`: The pipeline execution has been short-circuited by the system and never completed. * `DROPPED`: The pipeline execution has been dropped because the change has been rejected by the user following review.
        - `targetType` 'RELATIONSHIP' | 'RESOURCE' | 'OBJECT', required
        - `id` string, required — The ID of the resource created, upserted, or deleted.
        - `type` string, required — The type of resource created, upserted, or deleted.
      - object
        - `receivedAt` string, date-time, required — The time the operation was received.
        - `completedAt` string, date-time — The time the operation was completed (whether successfully or not).
        - `taskId` string, required — The task identifier. Used to track an async task in the system. Use the task ID to poll for completion status. The taskId holds different prefix to represent different tasks. - oneOf task: `s_<id>`. - bulk task: `bk_<id>` (deprecated: `<id>` only). - bundle task: `bd_<id>` (deprecated: `<id>` only). - purge task: `pg_<id>` (deprecated: `purge:<id>`).
        - `action` 'CREATE' | 'UPSERT' | 'DELETE' | 'UPDATE', required — The action to perform.
        - `status` 'SUCCESS' | 'PENDING' | 'CANCELLED' | 'FAILURE', required — Status of the operation. * `SUCCESS`: The operation was persisted in the source, or was dropped by a reject action of the user. * `PENDING`: The operation is being processed asyncronously by the system or is in a pipeline IN_REVIEW status. * `CANCELLED`: The operation was cancelled by the system due to a concurrent operation. * `FAILURE`: The operation failed due to validation or processing error.
        - `error` V1Error
          - `code` 400 | 401 | 403 | 404 | 408 | 409 | 413 | 500 | 501, required
          - `message` string, required
          - `type` 'ALREADY_EXISTS' | 'FAILED_PRECONDITION' | 'INTERNAL' | 'INVALID_ARGUMENT' | 'NOT_FOUND' | 'OUT_OF_RANGE' | 'UNIMPLEMENTED' | 'PERMISSION_DENIED' | 'UNAUTHENTICATED' | 'CONTENT_TOO_LARGE' | 'REQUEST_TIMEOUT', required
          - `details` V1Error[] — list of errors that occurred if applicable.
        - `pipelineExecution` V1PipelineExecutionInfo
          - `id` string, required — The id of the pipeline execution.
          - `pipelineDefinitionId` string, required — The id with version in the format `<id>.<version>`.
          - `status` 'SUCCESSFUL' | 'ERROR' | 'IN_PROGRESS' | 'IN_REVIEW' | 'CANCELLED' | 'DROPPED', required — Status of the pipeline execution. * `SUCCESSFUL`: The pipeline execution completed successfully. Every step of the pipeline was executed successfully and the change has been accepted in the system. * `ERROR`: The pipeline execution failed at a step due to a system error. * `IN_PROGRESS`: The pipeline execution is being processed by the system. * `IN_REVIEW`: The pipeline execution is waiting for a manual action. Refer to the ActOnPipelineExecution endpoint. * `CANCELLED`: The pipeline execution has been short-circuited by the system and never completed. * `DROPPED`: The pipeline execution has been dropped because the change has been rejected by the user following review.
        - `targetType` 'RELATIONSHIP' | 'RESOURCE' | 'OBJECT', required
        - `id` string, required — The unique identifier of the relationship. This is a key with the shape `{fromID}.{toID}`.
        - `type` string, required — The type of relationship created, upserted, or deleted.
      - object
        - `receivedAt` string, date-time, required — The time the operation was received.
        - `completedAt` string, date-time — The time the operation was completed (whether successfully or not).
        - `taskId` string, required — The task identifier. Used to track an async task in the system. Use the task ID to poll for completion status. The taskId holds different prefix to represent different tasks. - oneOf task: `s_<id>`. - bulk task: `bk_<id>` (deprecated: `<id>` only). - bundle task: `bd_<id>` (deprecated: `<id>` only). - purge task: `pg_<id>` (deprecated: `purge:<id>`).
        - `action` 'CREATE' | 'UPSERT' | 'DELETE' | 'UPDATE', required — The action to perform.
        - `status` 'SUCCESS' | 'PENDING' | 'CANCELLED' | 'FAILURE', required — Status of the operation. * `SUCCESS`: The operation was persisted in the source, or was dropped by a reject action of the user. * `PENDING`: The operation is being processed asyncronously by the system or is in a pipeline IN_REVIEW status. * `CANCELLED`: The operation was cancelled by the system due to a concurrent operation. * `FAILURE`: The operation failed due to validation or processing error.
        - `error` V1Error
          - `code` 400 | 401 | 403 | 404 | 408 | 409 | 413 | 500 | 501, required
          - `message` string, required
          - `type` 'ALREADY_EXISTS' | 'FAILED_PRECONDITION' | 'INTERNAL' | 'INVALID_ARGUMENT' | 'NOT_FOUND' | 'OUT_OF_RANGE' | 'UNIMPLEMENTED' | 'PERMISSION_DENIED' | 'UNAUTHENTICATED' | 'CONTENT_TOO_LARGE' | 'REQUEST_TIMEOUT', required
          - `details` V1Error[] — list of errors that occurred if applicable.
        - `pipelineExecution` V1PipelineExecutionInfo
          - `id` string, required — The id of the pipeline execution.
          - `pipelineDefinitionId` string, required — The id with version in the format `<id>.<version>`.
          - `status` 'SUCCESSFUL' | 'ERROR' | 'IN_PROGRESS' | 'IN_REVIEW' | 'CANCELLED' | 'DROPPED', required — Status of the pipeline execution. * `SUCCESSFUL`: The pipeline execution completed successfully. Every step of the pipeline was executed successfully and the change has been accepted in the system. * `ERROR`: The pipeline execution failed at a step due to a system error. * `IN_PROGRESS`: The pipeline execution is being processed by the system. * `IN_REVIEW`: The pipeline execution is waiting for a manual action. Refer to the ActOnPipelineExecution endpoint. * `CANCELLED`: The pipeline execution has been short-circuited by the system and never completed. * `DROPPED`: The pipeline execution has been dropped because the change has been rejected by the user following review.
        - `targetType` 'RELATIONSHIP' | 'RESOURCE' | 'OBJECT', required
        - `id` string, required — The ID of the object created or deleted.
        - `type` string, required — The type of object created or deleted.

## Other responses

- `404` — The task was not found.

---

[API](https://skmtc.dev/clinia/apis/registry-api.md) · [All operations](https://skmtc.dev/clinia/apis/registry-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/clinia/registry-api/revisions/3a9197b11351/schema)