Database endpoints
Check a background job
Check the state and progress of a filtered vector-record update or delete job.
GET /v1/tenants/{tenant}/vector-indexes/{index}/jobs/{job_id}
- Use the returned job IDIdentify the filtered update or delete.
- Inspect state and progressCompare examined, matched and applied work.
- Decide whether to continueBase follow-up actions on the reported outcome.
Before you start
Use your database bearer token.
Use the job ID returned by a filtered vector-record update or delete on this index.
Path parameters
| Field | Type | Required |
|---|---|---|
tenant | string | Required |
index | string | Required |
job_id | string | Required |
Headers
| Field | Type | Required | Description |
|---|---|---|---|
x-oc-db-user | string | Optional | Acting database user (role, grant and row-policy checks). Send with x-oc-db-key. |
x-oc-db-key | string | Optional | API key of the x-oc-db-user user. |
Read the result
Check state together with progress. Examined or matched records are not the same as updated records. A stopped or limited job can have applied some changes already.
Response statuses
HTTP status reference
| Status | What to do |
|---|---|
| 200 | OK |
| 400 | Correct the request before retrying. |
| 401 | Check the credential and Authorization header. |
| 402 | Check feature access or available credits. |
| 403 | Check tenant access, roles and permissions. |
| 404 | Check the resource ID and API route. |
| 429 | Honor Retry-After when present; back off. |
| 500 | Check the outcome before retrying a write. |
| 501 | Check deployment support for this operation. |
| 503 | Honor Retry-After when present; check write outcomes. |