---
title: "Get chunk deletion job status"
method: GET
path: "/local-file-groups/{id}/chunk-deletions/{chunk_deletion_id}"
tags: ["local-file-groups"]
---

# Get chunk deletion job status

`GET /local-file-groups/{id}/chunk-deletions/{chunk_deletion_id}`

## Request

- Base URL: `https://developer.qaip.com/api/v1`
- URL: `https://developer.qaip.com/api/v1/local-file-groups/{id}/chunk-deletions/{chunk_deletion_id}`
- Auth: API key in header `x-api-key`

Returns the status of a chunk deletion job previously started for the source group. The status is synced with the underlying execution on read on a best-effort basis: a finished job is normally reported as terminal (success or failure) immediately, but if the live sync fails the status may lag until the periodic reconciliation.

Required scope: \`ingestion:manage\`

## Path parameters

- `id` string, required
- `chunk_deletion_id` string, required

## Response `200`

Successful retrieval of chunk deletion job

- ChunkDeletion
  - `id` string, required: The id of the chunk deletion job
  - `source_group_id` string, required: The ID of the source group whose chunks are being deleted
  - `status` 'unknown' | 'queued' | 'not_started' | 'managed' | 'starting' | 'started' | 'success' | 'failure' | 'canceling' | 'canceled' | 'deleting' | 'delete_job_failure', required: Job status
  - `text_contains` string[], required: The substrings used to match chunk rows for deletion
  - `creation_time` integer: Unix timestamp when the job was created
  - `start_time` integer: Unix timestamp when the job started
  - `end_time` integer: Unix timestamp when the job finished
  - `deleted_count` integer, required: Number of chunk rows deleted. Always present; meaningful only once the job has succeeded (status = success). Before then it is 0 (not yet determined), so callers must gate on status rather than treating 0 as "no chunks deleted".

## Other responses

- `400`: Bad Request
- `401`: Unauthorized
- `404`: Not Found
- `500`: Internal Server Error
- `502`: The application proxy could not obtain an upstream response before forwarding response headers. The error code is unavailable and retryable is false: upstream side effects may have completed, so a 502 alone does not make retrying safe. Check the operation's idempotency and recovery contract before retrying. A failure after streaming has started instead aborts the stream without appending this JSON body. CDN or load-balancer generated errors may have a different body and are not described by this response.

## Changes

- **2026-09-17** `2489c6f1a9d8`: 17 info
  - added the non-success response with the status `502`
  - added the optional property `error/code` to the response with the `400` status
  - added the optional property `error/code` to the response with the `401` status
  - added the optional property `error/code` to the response with the `404` status
  - …13 more

[Operation history](https://skmtc.dev/qlonolink/apis/qaip-apis/changes/local-file-groups/:id/chunk-deletions/:chunk_deletion_id/get.md)

---

[API](https://skmtc.dev/qlonolink/apis/qaip-apis.md) - [All operations](https://skmtc.dev/qlonolink/apis/qaip-apis/llms.txt) - [OpenAPI document](https://skmtc.dev/qlonolink/apis/qaip-apis/revisions/2489c6f1a9d8?raw)