Retry Indexing Task
Restarts an indexing task whose run_state is failed or canceled under the same task ID and returns the updated task. Poll Get Indexing Task with the same ID afterwards.
To index the document again once the task is published, use Re-index Documents. For the re-index flow, see Re-index and Track Indexing.
An attempt with run_state: superseded cannot be retried, even though its stage is canceled. If you saved a newer task ID from a re-index response, poll that task.
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
run_state is dispatch_pending, and error and completed_at are null.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.