Cancel Indexing Task
Requests cancellation of an indexing task and returns the updated task.
If the task came from Re-index Documents, its bulk task counts the item as canceled. A bulk re-index has no cancel of its own, so stop one by canceling each of its tasks. For the re-index flow, see Re-index and Track Indexing.
Authorization
Path parameters
…/knowledge-fs/spaces/<knowledge base ID>), and the segment after /datasets/new/ in the address bar.compilation_job.id of a queued item in the Re-index Documents response, latest_task.id from Get Document, id from List Document Indexing Tasks, and the id of a document task in List Background Tasks.Responses
stage and run_state set to canceled and completed_at set.null while it runs and after a retry.asset.id of the Re-index Documents item that started the task, even when you submitted a document ID.failure.message. Set only when stage or run_state is failed. Otherwise null, including on canceled tasks.0, so repeated retries never exhaust the attempt budget on their own.Scheduler state of the current attempt:
dispatch_pending: accepted, waiting to be dispatched to a worker.queued: dispatched, waiting for a worker.running: a worker is executing the task.retry_wait: an automatic retry is scheduled, andstagestays unchanged.succeeded: accompaniesstage: published.failed,canceled: terminal.superseded: a newer attempt replaced this one. Terminal, reported withstage: canceled, and accepted by neither cancel nor retry.
null when not set. Retry Indexing Task sets it to dispatch_pending.
Indexing stage, in forward order:
queuedparsedoutline_builtnodes_generatedprojection_builtsmoke_eval_passedpublished
published means the new revision is active. failed and canceled are the other terminal values. Retry Indexing Task keeps the checkpoint the attempt had reached, so the value is rarely queued after a retry.